engineer-observability

Configure structured logging, metrics, distributed tracing, and alerting for production systems.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill engineer-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-observability
Source: https://github.com/thiagoooo34252/atlas-engineer/tree/main/skills/engineer-observability
Command: npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill engineer-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit provides tools and strategies for production observability, helping users to monitor, debug, and analyze system behavior efficiently.

Core Features & Use Cases

  • Structured Logging: Implement structured logging for better queryability and correlatability.
  • Metrics Collection: Collect and analyze metrics to understand system performance and availability.
  • Distributed Tracing: Trace requests across services for in-depth analysis.
  • Alerting Strategy: Set up alerting for critical system events and outages.
  • Health Checks: Implement health endpoints to assess service status.
  • SLOs and SLIs: Define and monitor Service Level Objectives and Service Level Indicators.
  • Dashboard Templates: Create operational dashboards for monitoring and incident response.
  • Alerting Rules: Define severity levels and conditions for alerts.
  • Reference Files: Provide detailed guidance on logging, metrics, and distributed tracing.
  • Cross-Skill References: Link to related skills for a comprehensive observability solution.

Quick Start

Use the engineer-observability skill to set up structured logging for your application.

Frequently Asked Questions about engineer-observability

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

FAQPage Schema
How do I implement structured logging for better queryability in production?

To implement structured logging, you format log entries as JSON objects with consistent fields, enabling better queryability and correlation across distributed system components during debugging.

What is distributed tracing and how does it trace requests across services?

Distributed tracing is a method to trace requests across microservices by propagating trace context, allowing in-depth analysis of request paths and identifying latency bottlenecks in production environments.

How do I set up alerting rules and severity levels for critical system outages?

Setting up alerting rules involves defining specific conditions and severity levels for critical system events, triggering notifications that enable fast incident response and minimize production outages.

How do I define and monitor SLOs and SLIs to measure system availability?

Defining SLOs and SLIs involves establishing measurable Service Level Indicators and objectives for availability and latency, then continuously monitoring them to evaluate production system reliability.

Can I create operational dashboard templates for monitoring and incident response?

Yes, you can create operational dashboard templates to visualize collected metrics, distributed traces, and health check statuses, providing real-time visibility needed for effective incident response.

Do I need health check endpoints to assess service status in production?

Yes, implementing health check endpoints is necessary to actively assess service status and availability, allowing monitoring systems to detect failures and trigger alerting during production outages.