Skip to main content

Configure Alerts

Epsagon alerts support many use cases: Kubernetes metrics, application performance metrics, and application exceptions.

Exception alerts#

Exception alerts are collected from the tracing libraries and available only for traced services and code

Screen Shot 2021-07-15 at 15.02.24.png

Manage your alert rules#

  • To manage your alert rules, go to Alerts
  • To create a new alert rule, click Create New Alert. To set up an alert for exceptions, go to the alerts page, and create a new "simple" alert. In the alert type - choose Exception.

Lambda Events#

Screen Shot 2021-07-15 at 14.48.03.png

Lambda event alerts are triggered for each Lambda invocation event of specific types.

  • Select event types to trigger the alert. Support events types are: Timeout, Out of Memory, Code Exception (available for traced functions), Function Error (identified by CloudWatch logs), Insight (function is close to the time limit or memory limit).
  • Filter which Lambda functions will trigger the alert by Application, specific Functions or AWS Accounts.

Lambda Metric#

Screen Shot 2021-07-15 at 14.49.23.png

Lambda metric alerts are triggered whenever Lambda invocations cross a specific threshold over time. For example, when the average number of invocations ending in timeout is greater than 10 invocations for a period of 15 minutes.

To create a Lambda metric alert:

  • Select an aggregation function
  • Select the invocation event on which to base the metric
  • Select an operator and the threshold value
  • Select the timeframe in which to check the metric value before triggering the alert

Trace Metrics Alerts#

Screen Shot 2021-07-15 at 14.50.33.png

Trace metric alerts trigger when a check on trace data is met. For example, when the average duration of putting items in a specific DynamoDB is longer than 2 seconds.

To create a trace metric alert:

  • Select an aggregation function
  • Choose filters to narrow down the metric. For example, filter traces by a Kafka stream name, or Kubernetes cluster.

Also, you need to create a threshold for your alert:

  • Frequency - How often the alert rule should be checked.
  • Evaluate For - For how long the threshold is checked. The threshold must be met for this amount of time in order to make the alert fire.

Select the conditions for your alert:

Screen Shot 2021-04-11 at 17.06.06.png

  • Reducer - Choose a reducing function for your query results.
  • Query - Choose what query to apply these conditions for.
  • From, To - Choose a timeframe for the alert's evaluation.
  • Operator - For comparison to the threshold.
  • Threshold - Your selected threshold.

Epsagon Metrics Alerts#

Screen Shot 2021-07-15 at 14.52.25.png

"Epsagon Metrics" alerts let you configure alerts based on metrics collected by your Prometheus. See our Kubernetes integration page for further info.

To create an "Epsagon Metrics" alert:

  • Select the metric you want to alert for.
  • Select an aggregation for the metric.
  • Filter the metric by specific filters.

See trace metrics alerts for threshold information.

Cloudwatch Metric Alerts#

Screen Shot 2021-07-15 at 15.00.17.png

Cloudwatch metrics alerts trigger when a Cloudwatch metric crosses a given threshold.

To create a Cloudwatch metric alert:

  • Select a namespace, and a stat to alert for.
  • Choose the dimensions to alert for. For example, a specific API, or all APIs.

Also, you need to create a threshold for your alert:

  • Frequency - How often the alert rule should be checked.
  • Evaluate For - For how long the threshold is checked. The threshold must be met for this amount of time in order to make the alert fire.

Select the conditions for your alert: