logging-telemetry-audit

Stars4

Forks0

UpdatedJuly 18, 2026 at 15:25

Audit logging, tracing, and metrics pipelines for volume waste — debug-level logging in production, unsampled traces, high-cardinality metrics explosions, duplicate log shipping, and retention without tiers. Use this skill whenever the user shares logging configs (log4j/logback/zap, OpenTelemetry, Prometheus, Datadog/Splunk settings), complains about observability costs, or wants a telemetry efficiency review. Part of Lean Agentic AI Skills; emits lean-findings.json.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

navveenb

navveenb/lean-agentic-ai-skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name

logging-telemetry-audit

description

Logging & Telemetry Audit

Producer skill — the brownfield sibling of data-minimization-designer, aimed at observability pipelines specifically. Input: logger configs, collector/agent configs, ingestion stats if available. Output: lean-findings.json.

Telemetry is data nobody asked for until something breaks — which makes it the easiest place for volume to grow unbounded. Every log line is charged the full four times (produce, ship, index, store), and indexing is the expensive, energy-hungry step people forget.

Subject type: emit subject.type: "observability" in findings.

Signatures

DEBUG/INFO in production hot paths — per-request logging at levels no one reads in steady state. High. Evidence: level configs + volume stats. Fix: WARN default with dynamic level raising (flip to DEBUG on demand during incidents — modern log frameworks support runtime level changes).
Unsampled tracing — 100% trace sampling at scale. High. Fix: head sampling at low rates + tail sampling for errors/slow requests (keep 100% of the interesting traces, sample the boring ones).
High-cardinality metric labels — user IDs, request IDs, or raw URLs as metric labels; series counts explode. High: each unique label combination is a stored, indexed time series. Fix: label allowlists, path templating (/users/{id}), histograms over per-entity gauges.
Duplicate shipping — same logs to two backends "temporarily, since the migration"; agents double-collecting (sidecar + node agent). Medium-high.
Logs as metrics — counting log lines in the backend to build dashboards that a counter metric would serve at a fraction of the volume. Medium. Fix: emit the metric, drop the log line.
No retention tiers — everything hot/indexed for the full retention window. Medium-high. Fix: short hot window (search-speed data), archive tier for compliance; pairs with storage-lifecycle-audit.
Verbose formats — pretty-printed JSON, stack traces on non-errors, request/response bodies logged whole. Medium. Fix: compact encoding, body logging only on error paths with size caps.
Collector inefficiency — no batching/compression on the shipping path (OTLP/agent batch settings at defaults). Low-medium.

Honesty rules

Ingestion volumes and series counts from the user's own stats are real numbers — report them. The named trade-off on every volume cut: diagnostic blind spots — pair each reduction with its incident-time escape hatch (dynamic levels, tail sampling, on-demand capture). Never recommend sampling error signals.

Cost signal (countable)

Cost drivers: ingested GB/day, retained GB × days, and billable metric series count. All three are countable from the platform's own stats; when available, name the exact driver and observed value in cost_signal.

Not this skill's job

What product data to collect at all (data-minimization-designer), where the archive lives (storage-lifecycle-audit).

More from this repository

same repository

agentic-loop-auditor

navveenb/lean-agentic-ai-skills

Audit agent frameworks and agentic workflows for token-burning loop pathologies — unbounded retries, excessive planning depth, tool-call thrashing, context snowballing, missing loop budgets and kill switches. Use this skill whenever the user shares agent configs or traces (LangChain/LangGraph, CrewAI, AutoGen, custom loops), complains an agent is slow or expensive, or is designing any autonomous/multi-step agent. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

ai-eval-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit AI evaluation infrastructure for wasted compute — full benchmark suites re-run on unchanged cases, LLM-as-judge grading without caching, oversized judge models, redundant eval passes per commit, and missing result reuse. Use this skill whenever the user shares eval harness configs or CI eval steps, complains that evals are slow or expensive, mentions LLM-as-judge costs, or runs benchmark suites on every change. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

api-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit API design for chattiness and over-fetching — REST endpoints requiring N calls per screen, GraphQL resolvers with N+1 fan-out, default-everything payloads, missing pagination and field selection, provider-side polling where webhooks serve, and uncompressed responses. Use this skill whenever the user shares API schemas (OpenAPI, GraphQL SDL), resolver code, endpoint designs, or asks why clients make too many calls or payloads are heavy. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

caching-strategy-designer

navveenb/lean-agentic-ai-skills

Design caching layers so work is done once, not per request — HTTP/CDN caching, application-level caches (Redis/Memcached), computed-result caching, and cache-invalidation strategy. Use this skill whenever the user wants to add caching, asks why the same work is recomputed, designs a read-heavy system, or an audit skill (db-efficiency-audit, web-carbon-audit) flags uncached repeated work. Part of Lean Agentic AI Skills; emits a cache design plus lean-findings.json.

2026-07-184

carbon-aware-scheduler

navveenb/lean-agentic-ai-skills

Design time-shifting of flexible workloads (batch jobs, CI, training, backups, crons) to hours and regions when grid electricity is cleanest, using carbon-intensity signals like Electricity Maps, WattTime, or the Carbon Aware SDK. Use this skill whenever the user mentions carbon-aware computing, scheduling flexible/deferrable jobs, demand shifting, running workloads when energy is clean, or asks how to reduce the carbon intensity (not just amount) of their compute. Part of Lean Agentic AI Skills; emits schedule designs plus lean-findings.json.

2026-07-184

carbon-budget-designer

navveenb/lean-agentic-ai-skills

Design per-feature and per-service efficiency budgets — page-weight budgets, token budgets per AI feature, query budgets per endpoint, GPU-hour budgets per training project — with owners, review checkpoints, and enforcement hooks. Use this skill whenever the user wants sustainability targets for teams, asks how to keep efficiency from regressing organizationally, mentions performance-budget-style governance for carbon/energy, or is setting engineering standards. Part of Lean Agentic AI Skills; an advisor emitting budget definitions plus lean-findings.json.

2026-07-184

name

logging-telemetry-audit

description

Logging & Telemetry Audit

Subject type: emit subject.type: "observability" in findings.

Signatures

DEBUG/INFO in production hot paths — per-request logging at levels no one reads in steady state. High. Evidence: level configs + volume stats. Fix: WARN default with dynamic level raising (flip to DEBUG on demand during incidents — modern log frameworks support runtime level changes).
Unsampled tracing — 100% trace sampling at scale. High. Fix: head sampling at low rates + tail sampling for errors/slow requests (keep 100% of the interesting traces, sample the boring ones).
High-cardinality metric labels — user IDs, request IDs, or raw URLs as metric labels; series counts explode. High: each unique label combination is a stored, indexed time series. Fix: label allowlists, path templating (/users/{id}), histograms over per-entity gauges.
Duplicate shipping — same logs to two backends "temporarily, since the migration"; agents double-collecting (sidecar + node agent). Medium-high.
Logs as metrics — counting log lines in the backend to build dashboards that a counter metric would serve at a fraction of the volume. Medium. Fix: emit the metric, drop the log line.
No retention tiers — everything hot/indexed for the full retention window. Medium-high. Fix: short hot window (search-speed data), archive tier for compliance; pairs with storage-lifecycle-audit.
Verbose formats — pretty-printed JSON, stack traces on non-errors, request/response bodies logged whole. Medium. Fix: compact encoding, body logging only on error paths with size caps.
Collector inefficiency — no batching/compression on the shipping path (OTLP/agent batch settings at defaults). Low-medium.

Honesty rules

Cost signal (countable)

Not this skill's job

What product data to collect at all (data-minimization-designer), where the archive lives (storage-lifecycle-audit).