skills.rest
reliant-labs
reliant-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

observability

Validate Forge observability stack health via Docker-based Grafana LGTM checks.

4|1|Updated Apr 12, 2026
Search Tags:#debugging#logs#metrics#observability#telemetry#grafana#traces
One-click install
npx skills add https://github.com/reliant-labs/forge --skill observability-reliant-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/observability
Command: npx skills add https://github.com/reliant-labs/forge --skill observability-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Observability gaps make it hard to diagnose production issues, because logs, traces, metrics, and profiling signals may be missing or disconnected. This Skill helps you confirm that your full Forge observability pipeline is running correctly so investigations start with evidence instead of guesswork.

Core Features & Use Cases

  • forge doctor health checks: Validates Docker containers, application health endpoints, pprof endpoints, Prometheus scrape targets, Tempo trace ingestion, Loki log streams, and Pyroscope profiles.
  • Signal-focused diagnosis: Checks only traces, metrics, logs, or profiles to narrow down failures quickly.
  • Grafana dashboards & navigation: Provides auto-provisioned Logs and Traces dashboards with Grafana access and search workflows.
  • End-to-end correlation: Ensures trace IDs propagate from logs to traces so you can jump directly to related telemetry.

Quick Start

Run forge doctor to verify the observability stack is healthy after you start your Forge project.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I verify my Grafana observability stack is running correctly?▼

Run forge doctor to verify your Grafana observability stack by checking Docker container health, application endpoints, and ingestion targets for logs, traces, metrics, and profiles.

Why are my application logs missing trace IDs?▼

Your observability stack may have disconnected trace IDs. Use health checks to validate log ingestion and ensure end-to-end correlation so trace IDs propagate correctly from logs to traces.

Can I check only specific telemetry signals like metrics or traces?▼

Yes, you can perform signal-focused diagnosis to check only traces, metrics, logs, or profiles. This narrows down failures quickly without validating the entire observability pipeline.

What is the best way to diagnose missing profiling data in local development?▼

The best way to diagnose missing profiling data is to validate pprof endpoints and Pyroscope profiles. This confirms your observability pipeline correctly ingests profiling signals for troubleshooting.

Does this observability validation support JSON evidence outputs?▼

Yes, the observability validation supports both JSON and verbose evidence outputs. This provides structured diagnostic data when verifying telemetry ingestion targets and application health endpoints.

Related Skills

Explore More Software Engineering Skills→
jovermierjovermier
1

coder-convex

Configure self-hosted Convex development in a Coder workspace with Docker.

Community
Advanced
pokgakpokgak

lgtm

Query Loki logs, Prometheus/Mimir metrics, and Tempo traces to investigate production issues.

Community
Advanced
osmanozenosmanozen

golang-benchmark

Analyze Go benchmarks, pprof profiles, and Prometheus metrics to quantify performance.

Community
Advanced
FernanSuozaFernanSuoza

obs-open-source-observability-stack

Implement and validate open source observability stacks with Prometheus, Grafana, Loki, Tempo, and OpenTelemetry Collector.

Community
Advanced