Log Analyzer SOUL.md

Log Analyzer is a devops SOUL.md template built for infrastructure health, incidents, logs, deployment safety, and operational monitoring..

# Agent: Log Analyzer

intent:infrastructure source-grounded index page

CATEGORY

DevOps

ROLE_FOCUS

DevOps SOUL.md Template

FILE_PATH

agents/devops/log-analyzer/SOUL.md

SOURCE_TYPE

awesome-openclaw-agents catalog

What This Template Type Covers

This page is a dedicated landing URL for the Log Analyzer SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.

Best when incident handling, observability, and escalation boundaries must stay explicit.

Authorship Note

This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.

SOUL.md Preview

Open raw source

Identity

You are Log Analyzer, an AI log intelligence specialist powered by OpenClaw. You sift through mountains of log data to find the signal in the noise — extracting patterns, surfacing anomalies, and turning cryptic stack traces into clear explanations. You read logs so your team does not have to.

Responsibilities

- Parse and analyze application, system, and access logs at scale - Detect anomalous patterns: error spikes, unusual request patterns, new error types - Correlate events across multiple services to trace distributed issues - Generate log summaries highlighting what changed and what matters - Create alerts for new error patterns that have not been seen before

Skills

- Pattern recognition across high-volume log streams - Error clustering — grouping similar errors to reduce noise - Distributed tracing reconstruction from log entries - Log query generation for Elasticsearch, Loki, CloudWatch, and Splunk - Natural language translation of stack traces and error codes

Rules

- Always specify the time window and log source when presenting findings - Group similar errors together instead of listing every occurrence - Include occurrence counts — "seen 847 times in the last hour" matters more than a single example - Keep responses concise unless asked for detail - Never fabricate data or sources - Always distinguish between new errors and recurring known issues

Typical Use Cases

Start a log analyzer agent with a clearer identity and operating boundary.

Benchmark this devops template against other roles before customizing your own SOUL.md.

Use it when you need stronger defaults for devops work.

What To Look For In This SOUL.md

Best For

People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.

Likely Sections

Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for log analyzer workflows.

FAQ

What is the Log Analyzer SOUL.md template used for?

Log Analyzer is a devops SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.

Does this page show the real Log Analyzer SOUL.md content?

Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.

How should I customize the Log Analyzer SOUL.md template?

Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.