Review application logging designs for structured fields, log levels, and telemetry correlation.
npx skills add https://github.com/RyoMa99/dotfiles --skill log-design
Please help me install this Agent Skill. Skill: log-design Source: https://github.com/RyoMa99/dotfiles/tree/main/dot_claude/skills/log-design Command: npx skills add https://github.com/RyoMa99/dotfiles --skill log-design
Provides clear guidance to design and review application logging so teams can reliably investigate incidents, reduce noisy logs, and ensure logs integrate with observability tooling.
Ask the skill to review a service's logging design and produce a prioritized checklist of missing fields, level adjustments, and telemetry correlation steps.
High-intent search queries and answers about installing and using this skill.
A canonical log line is a single, structured log entry per request that centralizes context and avoids duplication. You need it to improve observability and reliably investigate incidents without parsing scattered, noisy logs.
Design structured logging by separating data into constant fields for filtering, and manage log levels by aligning DEBUG/INFO/WARN/ERROR usage with monitoring rules to prevent alert fatigue and reduce noisy logs.
Correlate logs with traces by including trace ID and span ID in your structured log entries. This telemetry integration enables you to pivot between logs, metrics, and traces during incident investigation.
The best way to exclude PII and secrets is to enforce masking rules and environment-specific logging settings. This security and privacy strategy ensures sensitive data is never exposed in production observability tooling.
Yes, you can use a logging review checklist to audit production readiness. It evaluates design, content, and observability factors like missing fields, level adjustments, and telemetry correlation steps to ensure reliable incident investigation.
Deriving metrics from logs requires structured field hygiene because extracting numerical data depends on consistent field names. Managing field names as constants enables efficient filtering and reliable metric extraction from your telemetry.
rdkcentralAnalyze device log bundles with Telemetry 2.0 source code to identify issues.
pluginagentmarketplaceIntegrate Prometheus, Grafana, Loki, and OpenTelemetry for Kubernetes observability.
enigmaicon-engConfigure structured logging, Prometheus metrics, alerting, and OpenTelemetry tracing for AI services.
DoubleslashSEParse infrastructure logs to extract actionable insights for incident detection.
