In instrumental, we often talk about monitoring to begin with. In the past, we’ve covered important, but basic, metrics that everyone needs. Ultimate Monitoring Metrics Cheatsheet (many of which are aggregated by out-of-the-box systems and service monitoring). we have also written The Quick-Start Guide to Monitoring Your ApplicationWho initially discussed monitoring:
- your test suite
- your characteristics
- the inverse of your code coverage
But once you have your monitoring setup, how do you know if it’s time to expand the number or types of things you monitor?
It’s great to have comprehensive monitoring for every line of code and for every application interface, but it’s hard to implement (the Pareto Principle at work). Not to mention, too much monitor usually leads to information overload, and can waste a significant amount of time when searching for solutions to problems.
So how do you decide when to implement more surveillance? Two simple rules provide all the guidance you need:
If you have a question, and it takes more than a minute or two to answer it, you should write the relevant code. Catching through production server logs is not the answer, especially in the middle of a crisis. Monitoring is the fastest and easiest way to learn about the status of your production software.
If you need to see the result of changes in your application, make sure all relevant code is monitored. You should also annotate the change for easy visibility! When facilities are shipped or infrastructure is upgraded, use monitoring to ensure that changes have the desired result.
One of the reasons application monitoring is so effective is that you can measure business results and technical results in a single platform.
It often comes down to those two things. If you ever need an answer to a question, supervise it. If you are changing your application, monitor the change. Pretty soon, you’ll have enough important code to answer questions about the status of your application in seconds.
We think this highly focused metric is the best way to ensure that your application is performing at its best. While we offer the best server and system monitoring, Instrumental’s focus custom metric monitoring That is what separates us. let us know if you have any questions @ instrument