0

I have been having some difficulty understanding how to go about the ideal threshold for few of our cloudwatch alarms. I am looking at metrics for error rates, fault rate and failure rate. I am vaguely looking at having an evaluation period of around 15 mins. My metrics are being recorded at a minute level currently. I have the following ideas:

  1. To look at the avg of minute level data over a few days, and set it slightly higher than that.
  2. To try different thresholds (t1,t2 ..) and for a given day, see how many times the datapoints are crossing it in 15 min bins.

Not sure if this is the right way of going about it, do share if there is a better way of going about the problem.

PS 1: I know that thresholds should be based on Service Level Agreements(SLA), but let's say we do not have an SLA yet.

PS 2: Also does can I import data from cloudwatch to excel for some easier manipulation? Currently looking at running a few queries on log insights to calculate error rates.

sak18
  • 101
  • 13

1 Answers1

2

In your case, maybe you could also try Amazon CloudWatch Anomaly Detection instead of static thresholds:

You can create an alarm based on CloudWatch anomaly detection, which mines past metric data and creates a model of expected values. The expected values take into account the typical hourly, daily, and weekly patterns in the metric.

pba
  • 700
  • 8
  • 18