Log File Analyzer

Drop in a log export; get clustered errors with counts and a timeline — patterns surfaced, root cause left to you.

Build an agent that turns a raw log or error export into something you can read: clustered error signatures, how often each occurs, when they started and stopped, and the top offenders. It uses code interpreter to parse the file, normalize similar messages into clusters, and assemble a timeline — converting a wall of repetitive lines into a ranked, time-aware picture of what happened.

This is a single-tool analyze → error clusters pattern using XML-tag prompt structure. XML tags give a multi-phase job clean separation — <parse>, <cluster>, <report> — so each stage has one job and the agent doesn't blur parsing with conclusions. The defining discipline is restraint: it groups, counts, and times the errors and surfaces the patterns, but it does not declare a root cause as fact or recommend a production change — those are the on-call engineer's calls, made with the agent's summary in hand. Edge cases cover unstructured or mixed formats, enormous files (sample and say so), and logs with no clear errors.

This pattern applies anywhere a high-volume log needs to become legible. Common scenarios for this pattern:

• Incident triage prep
• Error-rate and crash-log review
• Post-deployment health checks
• Reducing a noisy-alert backlog
• Making an unfamiliar log readable

This manifest uses: code interpreter

How to build single-shot agents using xml tags prompt structure for report / tables output.

This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .

IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .