Skip to main content

Alerting Overview

Central Monitoring provides automated alerting capabilities by analyzing the data ingested from your applications. You can define custom rules to alert on specific patterns, errors, or conditions found in your log and metric data.

Contents​

How Alerting Works​

Central Monitoring continuously analyzes the data ingested from your applications to detect issues based on rules you define:

  1. Data Ingestion: Your application logs and metrics are ingested into Central Monitoring
  2. Rule-Based Detection: Custom alerting rules scan the ingested data for specific patterns, error conditions, or thresholds you've defined
  3. Alert Generation: When a rule condition is met, an alert is generated with relevant details from your data
  4. EventOps Processing: The alert is sent to EventOps for routing and notification based on your team's configuration
  5. Notification Delivery: EventOps delivers notifications via email, tickets, or other actions as configured

What You Can Alert On​

Based on the data ingested into Central Monitoring, you can create alerting rules for:

  • Log Patterns: Specific error messages, exception types, or log levels in your application logs
  • Field Values: Particular values or ranges in structured log fields (status codes, response times, etc.)
  • Frequency Thresholds: When certain events occur too frequently or stop occurring entirely
  • Metric Thresholds: When infrastructure metrics exceed defined thresholds
  • Custom Conditions: Any combination of field values, patterns, and logic that matches your monitoring needs

EventOps Integration​

Central Monitoring integrates with EventOps to handle alert routing, notifications, and incident management. EventOps is where you'll configure alertees, ticket creation rules, and how incidents are escalated.

If you're unfamiliar with EventOps, review the EventOps documentation to understand its capabilities.

Next Steps​