Key metrics for monitoring

A common mistake that companies with little experience in AWS monitoring make is trying to track as many metrics as possible, creating an overly complex system that is hard to maintain. ScienceSoft’s team of cloud support experts starts implementing monitoring by identifying the resources and events that affect the performance of your cloud applications. Our approach has a lot in common with Google’s “golden signals” and we recommend the following key metrics for monitoring:

• Latency: the time it takes to respond to a user request.
• Traffic: the number of user requests over a unit of time (usually per second).
• Errors: the number of requests that fail
• Saturation: measurement of how efficiently your resources are consumed.

Our team uses these key metrics as a basis and adds new indicators as we build up the system. The key here is to focus on tracking issues that actually affect your cloud applications’ performance and avoid collecting redundant metrics.

Our guide to applying monitoring rules

Rules form the architecture of your monitoring system. Here are some basic guidelines from our DevOps experts on rule creation:

• Monitored conditions should be urgent, actionable, and affect users.
• Defined rules should detect an otherwise unnoticed, unrecognizable condition.
• Rules should set alerts only for personnel entitled to resolve the type of issue at hand.
• Alerts and notifications should be reduced to a reasonable minimum.
• Responses to alerts should be automated to minimize human intervention.

More Info: checkpoint firewall jobs

About This Author

raviteja Joined: January 22nd, 2019