configure-log-aggregation SKILL.md skillA
configure-log-aggregation from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/configure-log-aggregation@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/configure-log-aggregation/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 15,102 bytes
- Repository stars
- 43
- License
- MIT
Set up centralized log aggregation with Loki and Promtail (or ELK stack), including log parsing, label extraction, retention policies, and integration with metrics for correlation. Use when consolidating logs from multiple services into a searchable system, replacing local log files with centralized queryable storage, correlating logs with metrics and traces, implementing structured logging with label extraction, or troubleshooting production incidents requiring cross-service log analysis.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Configure Log Aggregation Implement centralized log collection, parsing, and querying with Loki/Promtail or ELK stack for operational visibility. ## When to Use - Consolidating logs from multiple services or hosts into a searchable system - Replacing local log files with centralized, queryable log storage - Correlating logs with metrics and traces for full observability - Implementing structured logging with label extraction from unstructured logs - Setting retention policies for log data based on storage and compliance needs - Troubleshooting production incidents requiring log analysis across services ## Inputs - **Required**: Log sources (application logs, system logs, container logs) - **Required**: Log format patterns (JSON, plaintext, syslog, etc.) - **Optional**: Label extraction rules for structured querying - **Optional**: Retention and compression policies - **Optional**: Existing log shipper configuration (Fluentd, Filebeat, Promtail) ## Procedure > See [Extended Examples](references/EXAMPLES.md) for complete configuration files and templates. ### Step 1: Choose Log Aggregation Stack …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/configure-log-aggregation@sha256:203271cfd37b1be3The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_47pvqkn2a4czvjxe)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 19, 2026 and Aug 17, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | a784899 | 15,102 B | A | view · diff |
| v1.0 | 2026-04-19 | a31852a | 15,073 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 15,128 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15102 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_47pvqkn2a4czvjxe GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/configure-log-aggregation GET https://markdownregistry.com/api/v1/blob/203271cfd37b1be35de769d7ab7557eaaf3f6cdd2c810c7cd8ebcd413fcd95b7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.