This is an introduction to alerts in Moesif.
You may set up alerts to monitor your APIs to detect anomalies.
Alerts can be created under API Analytics -> Time Series. Check out Creating Alerts to read more on how to create alerts.
Alerts settings are specific to the org/app regardless ofvwho is signed in from your team.
If you have multiple organizations or apps like a Development and a Production app, each can have their own alert settings.
There are two parts to alerts: Alert Channels and Alert Rules
A channel is the medium you would like the alert to be sent to. At the moment, Moesif supports Slack, SMS, Email, and pagerduty as a channel. You can add many channels even for the same alert (i.e. you can send both a SMS and a Slack notification for the same alert).
API Alert Rules specify what you get notified on, when you get notified, and how often. Think of alert rules as a router or handler for new incoming alerts to outgoing channels. Every organization already has a default alert rule called
[Default] which cannot be deleted The default rule is the fallback rule if the URI Route of an error alert doesn’t match any user defined alert rules.
Alert rules are specific to a route like
POST /payout/:id enabling
handling of separate services differently. You can find a list of autodetected URI routes by going to API Analytics and selecting the URI Route filter.
The route field supports regex, so you can enter
/api/.* as an alert rule’s route. You can also specify multiple channels for the same alert rule (i.e. to notify multiple teammates) or if you want both email and Slack notifications.
I am not receiving any alerts
A: Moesif looks at both current and historical data when deciding to send alerts. If you deployed a new endpoint, there may not be enough historical data to make a decision. Give it a day running in production first. If you still are having issues, feel free to email us or adjust the detection sensitivity in dynamic alerts. Also, ensure you have an active channel under Alert Settings.
I am receiving too many alerts
A: If a particular endpoint like
GET /probe is noisy and generates many false alerts, you can add an explicit alert rule with 24 hrs as the maintenance window (i.e. always quiet) or increase the alert interval which will silence the route completely.