Modern operations teams are rarely short on data. A production incident can generate thousands of log lines, multiple dashboards, traces across several services, deployment events, alerts, chat messages, and customer reports. The harder problem is turning that data into shared understanding quickly enough for people to act.
Creating incidents often means filling out the same information over and over again. That’s why we’ve added Incident Templates – a faster way to create incidents using pre-configured settings. With templates, you can save commonly used incident details and apply them with a single click whenever you need them.
Need to compare one column to another? With the latest Alloy Navigator update, you can build dynamic field-to-field comparisons directly in data views. Spot overdue tickets, missed targets, and other exceptions in just a few clicks. Available in data views, Kanban boards, and interactive analytics.
In our previous article we looked at the basics of: In this article, we are going to take a deeper dive into some of the complexities of configuration as well as some of the nuances of analysing Claude telemetry. Before we dive into the code, let us just remind ourselves that our telemetry pipeline looks like this: That is, we are emitting Claude Code telemetry to an OpenTelemetry Collector. The telemetry is then exported to an Application Insights endpoint and stored in Log Analytics tables.