logging-metrics

Standardize structured JSON logging and metrics for observability across services.

1|2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/michaelsvanbeek/personal-agent-skills --skill logging-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-metrics
Source: https://github.com/michaelsvanbeek/personal-agent-skills/tree/main/skills/logging-metrics
Command: npx skills add https://github.com/michaelsvanbeek/personal-agent-skills --skill logging-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logs are not actionable without structure; this skill standardizes logging and metrics to improve observability across services.

Core Features & Use Cases

  • Structured Logging: enforce JSON logs with standard fields and contextual data.
  • Metrics & Dashboards: define the Four Golden Signals and enable dashboards for latency, throughput, and errors.
  • Use Case: ensure uniform logging across APIs, workers, and events to streamline incident investigation.

Quick Start

Configure your services to emit structured JSON logs to stdout and enable basic metrics collection for latency and error rates.

Frequently Asked Questions about logging-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize structured logging for observability across microservices?

Standardize structured logging by enforcing JSON logs with standard fields and contextual data across microservices, batch jobs, and serverless functions. This ensures consistent log schemas for compatibility with common dashboards, APMs, and alerting tooling.

What is the best way to define metrics and dashboards for API latency and errors?

Define metrics and dashboards by applying the Four Golden Signals to monitor latency, throughput, and errors. This enables consistent observability and alerting across APIs, workers, and events to streamline incident investigation.

How do I make logs actionable for incident investigation in serverless functions?

Make logs actionable by configuring serverless functions to emit structured JSON logs to stdout with standard and event-specific fields. This uniform logging approach streamlines incident investigation and ensures compatibility with APMs.

Does this structured logging approach work with existing APM and alerting tooling?

Yes, structured JSON logging works with existing APM and alerting tooling. It enforces standard fields and JSON formatting to ensure compatibility with common dashboards and monitoring infrastructure across services.

Why do I need structured JSON logging for batch jobs and workers?

You need structured JSON logging for batch jobs and workers because logs are not actionable without structure. Enforcing JSON formatting with standard fields ensures uniform observability and streamlines incident investigation across all service types.