Introducing chat-based data exploration with the Observability Agent
Services and applications produce massive amounts of telemetry – and making sense of all this data takes effort. Data is often spread across different stores, which means the way to clear insights goes through careful querying, refinement and correlation.
The Azure Copilot Observability agent now has a chat experience that simplifies this dramatically – you just ask, in your own plain, natural language.
Ask questions. Get answers.
To start chatting with the Observability agent, select a resource in the Azure Portal, and choose Logs from the resource menu. Click the Observability agent button. Soon, additional Azure observability experiences will show this or similar buttons so you can chat with the agent throughout your observability process.
The Observability agent chat opens with a short intro message, and a few suggested prompts. Select one of the suggestions or type your question in natural language:
“What errors increased in the last 24 hours?”
“¿Existen anomalías de latencia?” (are there any anomalies)
“どの依存関係が失敗しているか” (which dependencies are failing)
The agent translates your prompt into queries across all relevant data sources, analyses your data, and returns clear, data-backed insights – so you don't need to write KQL queries, switch between logs and metrics experiences, or dive into the schemas of your data store.
Explore your data – interactively
The chat experience is designed for an interactive process of data exploration and troubleshooting. Through the chat you can explore trends in logs and metrics, identify anomalies and visualize results directly in the chat – all from one interface.
Note: The agent operates here as your personal observability assistant - and it can only query data in your behalf, and access resources that you can access.
The chat with the agent has a progressive exploration flow, instead of isolated queries. Still, in each step in the conversation the agent provides a clear chain of thought, and in it - the actual queries it used - so you can keep clear track of how it understood your prompt, and created the provided output.
Results are show clearly and explained. In the example shown here, we follow up and ask the agent to create a time chart of the failed operations impacted by the errors it reported earlier. The result is clear - GET Customers/Details was impacted significantly, reaching 100K failed requests over a long time:
From exploration to guided investigation
The chat is very useful for guided investigations that go as deep as you choose, just as you would with the classic analysis tools over logs or metrics. Following the example shown above, we ask the agent to show exceptions or traces correlated with the failed requests:
The agent found an association to NullReferenceException, and suggests going deeper and use the operation_Id field to clearly identify the request -> dependency -> exception sequence. We'll accept the recommendation and choose the first suggestion: Pull full transaction timeline.
And here it is - each step of the transaction timeline explained, and the culprit is found - a failed Azure Table dependency.
We didn't have to write queries, review metrics, join tables or even know which tables are there. We used standard terms to ask questions in natural language, and we were able to get as deep as we wanted, and can dive deeper still. For example, you can tell the agent to:
- Map this call chain into a sequence-diagram style summary showing request, SQL dependency, table write, and exception.
- Calculate the average request latency during the last 6 hours, split by client type, location and OS
- Find anomalies in the exceptions logged over the last 4 hours
- Create a time chart to show the top 3 anomalies
- How many users were impacted by each of the top 3 anomalies found? Break down the exception counts by request operation
Launching a deep investigation
Through the chat with the observability agent, you can also trigger a full, deep investigation process.
A deep investigation doesn't handle just one question, but investigates an incident thoroughly - maps all related resources, identifies anomalies, performs correlations, analyzes root causes, and eventually provides a detailed report, including findings and recommendations. To start a deep investigation - select it from the suggestions provided during the conversation, or ask the agent explicitly, for example: run a deep investigation on the NullReferenceException anomaly.
Final thought
If observability used to start with queries – it now starts with a conversation. You can either guide the agent through the process you want to go through - or let it investigate on its own. Just ask.
Stay connected
- Follow this blog for ongoing deep dives, updates on current capabilities, and a preview of what’s coming next.
- Check out our recent public preview update of the Azure Copilot Observability agent.
- Live webinar
A walkthrough of real Observability agent scenarios, best practices, and what’s available today - along with a look at what’s coming next, and live Q&A with the product team. 👉 Register here
We’d love your feedback
The Observability agent continues to evolve based on real‑world usage and operator feedback. Share your thoughts directly through the Give Feedback option in the experience, or reach us at: azureobsagent@microsoft.com