Lesson213 words
Azure Monitor and Logs with DevOps tools
Configure Azure Monitor and Azure Monitor Logs to integrate with DevOps tools
The two data types
| Type | Nature | Queried with |
|---|---|---|
| Metrics | Numeric, time-series, cheap, retained briefly | Metrics explorer |
| Logs | Structured records, rich, retained longer | KQL |
Alert quickly on metrics; investigate in logs. A design that queries logs for every alert evaluation is slower and more expensive than one that alerts on a metric and uses logs for the follow-up.
Integrating with the pipeline
The valuable connections run in both directions:
| Direction | Example |
|---|---|
| Pipeline → Monitor | Annotate a release so telemetry shows when a deployment happened |
| Monitor → Pipeline | Query Azure Monitor alerts as a check, blocking deployment to an unhealthy target |
Release annotations are what let you answer "did the error rate rise after we deployed?" on the chart rather than by cross-referencing timestamps by hand.
Workspaces
Logs are stored in a Log Analytics workspace. Deciding how many you need is a real design question: one workspace makes cross-service queries easy, several give tighter access control and separate retention. Data residency and who may read production telemetry usually decide it.
Primary sources