DevOps Monitor – Continuous Monitoring


Continuous Monitoring – Introduction

DevOps Articles

Monitoring is not new, but continuous monitoring goes one step further. This article is about what may be expected from monitoring continuously.

Continuous Monitoring – Definitions

Key Performance Indicator (KPI)

The KPI is defined to measure a Critical Success Factor (CSF). A CSF is a counter measure for a risk that a target is not achieved.

Continuous Monitoring – Concepts

Continuous Monitoring is an essential part of DevOps, which not only monitors software (resources) but also developers (people) and development processes (methods). The resources are measured continuously in all environments to find errors as early as possible. The people are measured in terms of competence development (knowledge, skills and attitude) and the method includes measuring velocity (processing capacity) and efficiency.

Continuous Monitoring – Best Practices for DevOps release

This article starts with the best practices of continuous monitoring and continues to describe what continuous monitoring is about.

Monitoring Best practices

  • Start as soon as possible with monitors in the DTAP street, not just in production.
  • Establish defects as soon as possible based on the monitor device that is also used in production.
  • Monitor not only the software but also the DevOps team.

Monitoring KPI’s per phase

Monitoring of the DevOps phases might consist of:

  • Development process
  • Velocity
    • TTM
    • Escaped defects
    • Competences
  • Continuous Integration
    • Number and percentage of manual tasks
    • Drop in the delivery pipeline
  • Continuous Testing
    • Number of (recurring) defects
    • Coverage
    • Percentage of manual tests
    • Defects per stadium in de delivery pipeline
    • UT, ST, SIT, preFAT, preUAT, prePAT, Fat, UAT PAT, PST in the D-T-A-P
  • Continuous Delivery

Montoring Means

  • Monitoring based on tollgates:
    • DOR
    • DOD
    • Promotion
    • Radiator
  • Monitoring based on SLA-norms
    • Non functional requirements monitoring in the OTAP
    • Reporting on lead times
  • Monitoring based on Admin tools
    • Number of defects
    • Number of user stories
  • Monitoring based on automation
    • Regression test tools (defects)
    • ‘energyindicators ‘ a-la Tiobe (deviations standards – rules – guidelines)
  • Monitoring based on meaurements
    • Performance monitoring
    • Capacity usage monitoring
    • Availability monitoring

Monitor tools

There is a large set of monitor tools in the market that can be used for Continuous Monitoring.

Examples are:

  • Splunk
  • Gensys (SPS)
  • Nagios
  • SCOM
  • Et cetera
LinkedIn Group

Discuss with us about this article on LinkedIn.

More information

Related Books:

DevOps Best Practices, ISBN: 9789492618078
Agile Service Management with Scrum, ISBN: 9789071501807

Related training sessions:

Related Article:

Service Management

Samenvatting
DevOps Monitor - Continuous Monitoring
Artikel
DevOps Monitor - Continuous Monitoring
Beschrijving
Monitoring is not new, but continuous monitoring goes one step further. This article is about what may be expected from continuous monitoring.
Auteur
Publisher Naam
ITpedia
Publisher Logo
Sidebar