Application- versus service- versus component-level telemetry
As covered in Chapter 7, Microservice Observability, we can collect simple telemetry by installing the Application Insights library as a dependency and configuring it to point to an existing Application Insights instance in Azure. This covers us at the code level for any immediate metrics, logging, or tracing that Application Insights can provide out of the box. While this is useful, we may need to break that down further and capture some specific baselines at various levels.
For our sample application, we would expect to capture telemetry at three different levels:
- Application – Telemetry at the application level would include the overall health of the application, as well as any critical failures and the ability to troubleshoot distributed services. This may also include infrastructure- or cloud-platform-related status indicators.
- Service – Telemetry at the service level would include measurements...