Feature Request: Automatic Retrieval of DNS Records for Bot Monitoring

I’d like to request a feature that allows the software to automatically fetch DNS records and add them to the bot monitor. This would help save time and streamline the process instead of manually adding them.

Template or Recommend wizard

For UX, when user enter the domain we should recommend with some common template. Ex, when add domain we recommend they to add ssl, domain-expire, and health-check,…

Diverse context for health checking

I suppose when a web page update a package that not support Safari old version that will cause some problem on randomly device. I propose Bubobot should provide solution for those situations. Reproduce the context and report it to users.

Parse curl

Should have function to automatically import api from curl

Update tag follow domain

I should tag follow domain when setting.

Unhealthy container alert

Subject: Feature Request: Health Status Alerts for Containers Dear Team, I would like to propose a feature enhancement regarding container health monitoring. Currently, there are no alerts triggered when a container becomes unhealthy. I believe it would be beneficial to implement an alerting system that notifies users when a container's health status changes to unhealthy and resolves the alert once the container returns to a healthy state. This feature would greatly enhance our ability to maintain system reliability and respond promptly to issues. Thank you for considering this request! Best regards, Ajay Kumar ( Mr Cloud Book )

Client Agent

We should have an agent to run on the customer server, then collect data (such as port running, service running, debugging log…) and send it to our monitoring system

Integrations feature

We should let users add other platform accounts ( Ex: Google Chat, Telegram, Discord..). via platform SDK instead of inputting webhook links (Ex: Google Chat, Discord..) or token and chat ID (Telegram)

Kafka monitor type: optimization

I propose some features that can be compatible into bubobot : Monitor from 2 side: Producer: produce messages on target topic. you should check a kafka producer client can be push messages on target endpoint, topic. Consumer: subscribe the messages from target topic, you should check a consumer client can be pull message form target endpoint, topic. Bootstrap server: it’s can be a broker or a intermediator server for broadcast and advertise others TLS/SSL: provide a field can be enter the self-signed or CA file to allow secure connection to server.

Tooltip: a note specify extra information about something when the user moves the mouse pointer over or click on

I’d like to know what field function mean. better case, it could be suggest some common examples for that filed. Make it easy and make sense.

Monitor type: MQTT message on success field is optional

It’s not work when “success message“ not defined while my MQTT service are running healthily. Just in case, the last message return from the Topic is correct with this field; in the rest, without any case can return as expected.

Pipeline monitoring

I would like to see a pipeline monitoring feature. It may contain a few steps to complete the monitoring while there are some features can not be completed in one api but they need a few steps with serveral time to be completed. Thanks #pipeline #monitor #multiple

Select multiple alert at once can be nice

When adding my website to the monitoring dashboard, I can only select one alert monitoring option at a time. It would be more convenient if I could choose multiple alert options on the screen at once, so I only need to set it up once and then start monitoring.

I think you need to add the SSO, and the product can manage the users like group department.

Extended Response Time History

Bubobot currently provides a chart showcasing response time data for the past week. However, I want to access more extended historical data (e.g., 3 months) to analyze trends, identify seasonal patterns, or investigate long-term performance changes.

Incident Management Page

We propose adding a dedicated "Incident Management" page within Bubobot. This page would provide a comprehensive overview of all current and historical incidents and offer efficient management and analysis tools.

Tagging Alerts for Filtering and Organization

While Bubobot generates various alerts, there's currently no way to categorize or group them using tags. This can make it challenging to quickly identify specific types of alerts or filter through large volumes of alerts.

Incident Management with Team Assignment

I propose integrating incident management capabilities into Bubobot, allowing users to: Create Incidents: Automatically or manually convert alerts into trackable incidents within Bubobot. Assign Incidents: Assign incidents to specific team members or groups responsible for addressing the issue. Track Progress: Monitor the status of each incident (e.g., open, in progress, resolved) and track resolution time. Collaboration: Facilitate communication and collaboration among team members within the incident context (e.g., comments, notes). This feature would significantly enhance Bubobot's value for teams by streamlining incident management, improving collaboration, and reducing downtime.

Monitor Duplication

I suggest adding a "Duplicate Monitor" functionality to Bubobot. This feature would allow users to quickly create a new monitor by duplicating an existing one and then modifying only the necessary settings (e.g., URL, keywords).

Response Time-Based Alerts

I propose adding a new alert type focused on response time thresholds. This will allow users to define customized parameters for acceptable response times and receive alerts when those thresholds are exceeded.