DevOps – Stage 3: Do you know what metrics to collect?
  v7.0 Posted at 5/04/2017 5:10 AM by Tiago Araujo

Now that your team is spending less time deploying the application, you’ve got more time to improve other aspects of the application, but first you need to know what to improve. 

Here are a few easy things to gather metrics on:

Application Logging (Exceptions)

See how many errors are being produced, aim to reduce this as the produce matures

But it's not only exceptions you should be looking at but also how your users are using the application, so you can see where you should invest your time

  • Application Insights - https://rules.ssw.com.au/why-you-want-to-use-application-insights
  • Google Analytics
  • RayGun.io (Pulse)

Application Metrics

Application/Server performance – track how your code is running in production, that way you can tell if you need to provision more servers or increase hardware specs to keep up with demand

  • New relic


Process Metrics

Collecting stats about the application isn't enough, you also need to be able to measure the time spent in the processes used to develop and maintain the application. You should keep an eye on and measure:

  • Sprint Velocity
  • Time spent in testing
  • Time spent deploying
  • Time spent getting a new developer up to speed
  • Time spent in scrum ceremonies
  • Time taken for a bug to be fixed and deployed to production

Code Metrics

The last set of metrics you should be looking at revolves around the code and how maintainable it is. You can use tools like:

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address:


    Note: Social Media login for Yotpo is not working in IE or Safari, please use Chrome. We are waiting for Yotpo to fix it.