FAQs

Threshold-based anomaly detection works immediately. AI-powered detection requires 14 days of historical data to establish accurate baselines.

We monitor your systems from multiple global locations to provide accurate, region-specific insights. Check our coverage at https://docs.bubobot.com/configuration/worker-ip-locations 

Bubobot AI collects response time data for 14 days to understand your application's normal behavior patterns, including daily cycles, weekly patterns, and typical variability before activating anomaly detection.

Alerts for the selected monitors are automatically suppressed for the scheduled time.

Bubo AI is trained exclusively on verified Bubobot documentation and updated regularly. For complex account-specific issues, it will recommend contacting our support team.

A monitor run occurs each time our system checks your endpoint or service. The total number of monitor runs is calculated by:

• Frequency of checks (e.g., every 30 seconds)
• Number of enabled workers (each worker counts as a separate run)

For example:

• 1 monitor with 1 worker checking every minute = 1,440 runs/day
• 1 monitor with 4 workers checking every minute = 5,760 runs/day (1,440 × 4 workers)

Monitor runs accumulate across all your active monitors and their respective workers.

When creating or editing a monitor, select the Anomaly Detection tab and choose between two powerful options:

• Bubobot AI: Our intelligent system that automatically learns your service patterns and detects anomalies based on your chosen sensitivity level (e.g., 80% means alerting when metrics drift 80% from normal)
• Threshold: Set specific static values (like 5000ms response time) as your performance boundary

With either option, you can customize when alerts trigger by setting what percentage of checks must exceed limits and for how long.

1. Click on the Bubobot icon in the top-right corner of your dashboard
2. Type your request in natural language, such as:
   • "Set up Slack notifications for all production monitors"
   • "Show me all critical incidents from the last 24 hours"
   • "Pause monitoring for the dev environment during our deployment"
3. Review the assistant's response and confirm any actions
4. Continue the conversation for follow-up tasks or questions

Escalation policies help ensure critical alerts are never missed. They allow you to:

• Define multiple levels of responders
• Set time-based escalation rules

For example, if the primary responder doesn't acknowledge an alert within a specified time, it automatically escalates to the next level of support.

Yes, you can set up a custom domain for your status page (e.g., status.yourcompany.com).