grafana-lgtm

Visualize local OpenTelemetry telemetry in Grafana LGTM for Navigator.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neon-law-foundation/navigator --skill grafana-lgtm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grafana-lgtm
Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/grafana-lgtm
Command: npx skills add https://github.com/neon-law-foundation/navigator --skill grafana-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you verify that Navigator is emitting traces, logs, and metrics correctly by showing them in a local Grafana LGTM stack instead of guessing from stdout or waiting for production.

Core Features & Use Cases

  • Automatic local observability stack: Starts Grafana, Loki, Tempo, Prometheus, and the bundled OTel Collector as part of the KIND development flow.
  • Cross-service trace inspection: Confirms trace propagation from web into workflows-service across the Restate boundary.
  • Safe telemetry validation: Verifies identifiers, counts, statuses, and durations without logging client content or legal text.
  • Use case: Check that a new span, counter, or log field appears in Grafana before shipping a change to production.

Quick Start

Run navigator start-dev-server, generate a request or workflow, and open Grafana at http://localhost:3000 to inspect the resulting traces, logs, and metrics.

Frequently Asked Questions about grafana-lgtm

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

FAQPage Schema
How do I visualize local OpenTelemetry traces in Grafana during development?▼

You can visualize local OpenTelemetry traces in Grafana by running a KIND-based development flow that automatically starts Grafana, Loki, Tempo, and Prometheus with an OTel Collector. Open Grafana at localhost:3000 to inspect the resulting telemetry data.

How do I verify cross-service trace propagation across Restate boundaries locally?▼

Verify cross-service trace propagation across Restate boundaries by inspecting traces in the local Grafana LGTM stack. It confirms trace propagation from web requests into workflows-service, allowing you to validate distributed spans before shipping changes.

Can I use Prometheus and Loki to inspect local KIND cluster metrics and logs?▼

Yes, you can use Prometheus and Loki to inspect local KIND cluster metrics and logs. The stack runs these datasources alongside Tempo and Grafana, requiring automatic OTLP export and port-forwarding to visualize telemetry from your local environment.

What is the best way to debug local web telemetry without waiting for production?▼

The best way to debug local web telemetry without production is using a local Grafana LGTM stack. It captures traces, logs, and metrics via an OTel Collector, letting you confirm new spans or counters appear locally before deploying changes.