Alerts
Create alerts on metrics, log patterns, or trace conditions (e.g. error rate, latency, or specific errors). When a condition is violated, Rocketlog can notify your team via the channels you configure (e.g. Slack, PagerDuty, email).- What you can alert on — Metric thresholds, log volume or content, trace error rate or duration, and similar signals that Rocketlog ingests via OpenTelemetry.
- Where to configure — Set up alert rules in the Rocketlog dashboard under Alerts. You choose the metric or query, the threshold, and the notification target.
SLOs (Service Level Objectives)
Define SLOs (e.g. “99.9% of requests under 200ms” or “99% success rate”) so you can track reliability over time. Rocketlog uses your ingested metrics and traces to compute SLO compliance and can alert when you burn too much error budget.- Typical SLOs — Latency (e.g. p99 < 500ms), availability (e.g. success rate > 99%), or custom metrics you send via OpenTelemetry.
- Error budget — When your SLO is at risk or the error budget is exhausted, you can trigger alerts or runbooks so the team can respond before users are impacted.
Smart alerting and grouping
We group related alerts to reduce noise:- Multiple conditions firing for the same underlying issue (e.g. same service, same time window) are grouped into a single notification where possible.
- You see one consolidated alert with context instead of dozens of similar pages.
Getting started
- In the Rocketlog dashboard, go to Alerts or SLOs.
- Create an alert rule or SLO using the metrics and queries available from your OpenTelemetry data.
- Configure notification channels (e.g. Slack) and, if needed, connect the Slack integration for on-call AI SRE.