Alert Configuration
Alerts in Applicare can be static thresholds, adaptive baselines (via IntelliSense), or composite conditions. This guide covers creating a condition, setting severity, and routing notifications.
Creating an alert#
From any metric, choose Create alert. Pick the condition type:
- Threshold: fixed value, e.g. disk > 90%.
- Baseline: deviation from the learned norm — best for latency, throughput, error rate.
- Composite: combine conditions (e.g. error rate up and latency up).
Severity & de-duplication#
Assign a severity (info / warning / critical) and an evaluation window to avoid flapping. Related alerts on connected entities are automatically grouped so a single root cause doesn't page ten people ten times.
Notification channels#
Route by severity and tag to email, Slack, PagerDuty, ServiceNow, or a webhook. Configure channels once and reuse them across alerts.
severity: critical
match: team:payments
notify: [ slack:#payments-oncall, pagerduty:payments ]See Slack · Jira · Prometheus and Webhooks for channel setup.
Was this page helpful?
Can't find what you need?
Ask ArcIn or reach our support engineers.