Exception tracking reports application exceptions to a service that deduplicates them, alerts developers, and tracks each resolution. In microservices, it supports diagnosing problems when requests cross multiple services and there is no single log file to examine. section 7.6.2
Exception tracking
The collection, deduplication, alerting, and resolution tracking of application exceptions.
How Microservices Patterns, Second Edition covers it
- How deep it goes
- Defines reporting, deduplication, alerting, and resolution tracking, but defers implementation details.
- What you can do after
- Operate exception tracking by reporting exceptions to a service that deduplicates them, alerts developers, and tracks resolutions.
- How it connects
- Connects exception tracking with observability, log aggregation, distributed tracing, application metrics, health check APIs, and audit logging.
This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.
