From the course: AWS for DevOps: Monitoring, Metrics, and Logging

Unlock the full course today

Join today to access over 22,400 courses taught by industry experts or purchase this course individually.

Key considerations for monitoring

Key considerations for monitoring - Amazon Web Services (AWS) Tutorial

From the course: AWS for DevOps: Monitoring, Metrics, and Logging

Start my 1-month free trial

Key considerations for monitoring

- [Instructor] So to pull this all together, to implement successful application AWS monitoring and logging, I recommend that you look at these key business considerations. Application Availability, and what I mean by that is what is the business requirement for the application uptime. This is usually defined in the number of nines. So this could be four nines, five nines, so 99.999 percent uptime, so on and so forth. And, I recommend that this is written down and formalized in a service level agreement, as I talked about in a previous movie. That way, the teams have a goal to shoot for, and they can set up the monitoring to meet that. Secondarily, Performance is almost always one of the business goals. Again, as with Availability, I recommend that the Performance goals are defined in the SLA. And those include metrics, such as, time to reach a webpage, time to complete an order on a website, and so on and so forth. The important point, is that the metrics and logging should be driven…

Contents