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.

Outcome-based monitoring

Outcome-based monitoring - Amazon Web Services (AWS) Tutorial

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

Start my 1-month free trial

Outcome-based monitoring

- [Instructor] When you're working with your team to determine your monitoring strategy, I use this as a template for the discussion, and I call it outcome-based monitoring. And, these are based on key service tenants. So, as I've been mentioning, every group that I've worked with is always concerned with availability, so is your application working? Is it up? That's pretty key and core, but you might be surprised at how many times I've seen people actually just assume someone else is doing this, so I don't want to skip over the obvious. After the first outcome, then the list might vary, and this is just an example from one customer. The second outcome they were looking for was performance. Is it fast? Now, fast, of course, is relative, and I'll get into in a minute a way that I use to help teams to define what fast means across the organization, 'cause this can cause quite a lot of trouble if you don't closely define it, because it means one thing to one group, and a different thing…

Contents