Intelligent Alerting & Notifications

Bleemeo supports multiple notification channels: Email with rich HTML formatting and embedded metric graphs, SMS for critical alerts with global coverage, Webhooks for integration with Slack, PagerDuty, Microsoft Teams, OpsGenie, and custom endpoints, and Mobile push notifications through the Bleemeo iOS and Android apps. You can configure multiple channels per alert rule.

Bleemeo provides pre-configured alert rules for common infrastructure issues (high CPU, low disk space, service down, etc.) that activate automatically when you connect servers. For custom alerts, you can define threshold-based rules on any metric with configurable warning and critical levels. Advanced users can use PromQL queries for complex alerting conditions.

Bleemeo uses machine learning to automatically detect unusual patterns in your metrics. Rather than requiring static thresholds, the system learns what's "normal" for each metric over time. When behavior deviates significantly from expected patterns, an alert is triggered. This catches issues that would be missed by traditional threshold alerts, like gradual performance degradation or unusual traffic patterns.

Yes, Bleemeo supports alert routing based on multiple criteria. You can route alerts by service type (database alerts to DBAs, web server alerts to ops), severity level (critical to on-call, warnings to email), time of day (different contacts for business hours vs after-hours), and custom tags. Each route can use different notification channels.

Bleemeo includes several features to reduce alert noise: Alert grouping combines related alerts into single notifications, Alert dependencies suppress downstream alerts when root cause issues are detected, Rate limiting prevents notification floods, and Maintenance windows suppress alerts during planned work. These ensure you're notified about real issues without being overwhelmed.

You can define multi-level escalation policies. If an alert isn't acknowledged within a specified time, it automatically escalates to the next level - perhaps from email to SMS, or from primary on-call to backup. This ensures critical issues don't get lost even if the first responder is unavailable. Each escalation level can have different contacts and channels.

Maintenance windows let you suppress alerts during planned work. You specify a time range and optionally which hosts or services are affected. Monitoring continues during the window (so you have data), but alerts are held back. This prevents false alarms during deployments, updates, or scheduled maintenance. You can create recurring windows for regular maintenance schedules.

Yes, Bleemeo provides a complete event history showing when alerts triggered, changed state, and resolved. You can filter by service, severity, and time range. This history is valuable for post-incident analysis, understanding recurring issues, and tracking mean time to resolution (MTTR). Events can be exported for reporting or compliance purposes.

Yes, Bleemeo's webhook integration sends JSON payloads to any HTTP endpoint. The payload includes alert details, metric values, host information, and timestamps. This enables integration with custom ticketing systems, incident management platforms, chat tools, or automation workflows. You can customize which alerts trigger webhooks and to which endpoints.

Alert notifications are sent within seconds of an alert condition being detected. Metrics are collected every 10 seconds, and alerts are evaluated continuously. Email and webhook notifications typically arrive within seconds; SMS may take slightly longer depending on carrier. Push notifications to mobile apps are near-instantaneous for users with the app installed.