11 Monitoring and analytics: Measuring API product metrics

 

This chapter covers

  • Measuring API product analytics: API usage, time-to-first call, and active consumers
  • Measuring API monitoring metrics: latency, traffic, and error rates

In chapter 1, you learned that APIOps is the end-to-end automation of the development life cycle using DevOps and GitOps principles. One of the DevOps principles, as presented by Gene Kim, is the principle of using continuous feedback to detect and fix problems in the software value stream. One way this is implemented is by the DevOps practice of continuous monitoring and measurement. This continuous monitoring and measurement is about collecting, analyzing, and sharing metrics from the production system with the development team to foster a cycle of improvements. It involves monitoring—using predefined metrics, dashboards, and alerting to understand, query, and analyze the behavior of running systems, as well as resolve problems.

11.1 API product analytics: The business challenge

11.1.1 API product development as a PDSA cycle

11.1.2 The developer journey map

11.1.3 API product metrics

11.1.4 Tracking metrics for the Product Catalog API

11.2 API monitoring metrics

11.2.1 RED metrics

11.2.2 Rate limits

11.2.3 Monitoring tools

11.2.4 Alerting and synthetic monitoring

11.2.5 Service level indicators, service level objectives, and service level agreements

11.3 Wrapping it up

Summary