[
Edgesight · Alerts]
Edgesight Alerts watches your CDN traffic for error spikes, cache drops and slow origins, and tells you on Slack, email or a webhook. Start from a template or build your own rule; you hear from it only when something needs you.
Features
Rules on your CDN traffic, sent where your team works, with reminders paced so a long incident does not flood the channel.
Alert rule
Fires when error rate > 5% over 15m
Start from a template for the common CDN cases, or build from scratch: a metric, a condition, a value, an evaluation window and how often to check. Narrow it by server name or HTTP status code.
Pick one per alert, on any metric
Threshold fires above or below a fixed value. Percentage fires on a change against the previous window. Trend learns your traffic from the last two days and fires on a real deviation, not on natural swings.
Alerts land in a Slack channel integrated with Edgesight, with a chart of the recent traffic and the alert’s description if you want them.
Each alert goes to one destination: a Slack channel, one or more email addresses, or a webhook POST for PagerDuty, Opsgenie or your ticketing system. Need two channels? Define the alert twice.
Each alert keeps its trigger times, the traffic around them and the notifications sent. Tune the threshold against what actually happened.
Remind every
Only while the alert stays triggered
While an alert stays triggered, a reminder goes out at the interval you choose: 10 to 15 minutes for critical alerts, an hour or more for informational ones.
Overview
Triggered and notified alerts across your rules. Notified can be lower: the interval holds back repeats.
How it works
The Create Alert wizard, from the Alerts overview. Every alert can be paused, edited or deleted later.
Pick one of the ready-made alerts for common CDN cases, or choose Custom Alert to start from scratch.
Detection type, metric, condition and value, the evaluation window and the check frequency, then filters if you need them.
Slack, email or a webhook, and the interval for reminders while the alert stays triggered.
Name the alert, add a description for your team, check the summary and create it. It starts checking right away.
Destinations
Three destinations, one per alert. For more than one channel, define the alert again with the same rule.
A channel integrated with Edgesight
LiveOne or more addresses
LiveHTTP POST to your URL
LiveStart from a template and your first alert is checking your traffic in minutes.
Get started
