원클릭으로 Manus에서 모든 스킬 실행

grafana-lgtm

스타4

포크0

업데이트2026년 7월 4일 19:18

`navigator dev up` stands up the KIND stack with Grafana LGTM (Loki logs + Tempo traces + Prometheus metrics + a bundled OTel Collector) so you can actually SEE the telemetry every Neon Law Navigator binary emits — it wires both in-cluster and host-side `web` to export to it and port-forwards Grafana to the host. Trigger when asked to "see traces locally", "test OTel output", "check logs/metrics/traces in Grafana", "is my span showing up", to debug a cross-service trace (`web` to Restate to a workflow handler), or to verify a new metric/span before it ships to prod. This is the LOCAL viewing loop; the emit-side seam (how to ADD a span/metric/log and the no-content rule) is the `observability` skill, and the prod landing (Cloud Trace / Cloud Logging / BigQuery) lives there too.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

neon-law-foundation

neon-law-foundation/navigator

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Seeing telemetry locally with Grafana LGTM

Emitting OpenTelemetry through telemetry::init is only half the loop. This skill is the other half: a local sink that shows the traces, logs, and metrics so you can confirm they're shaped right before they ever reach prod's Cloud Trace / Cloud Logging. All the facts live in the doc — read docs/observability.md (§ "Seeing telemetry locally: Grafana LGTM") and keep it, not this skill, authoritative: the bring-up, the Grafana Explore queries per datasource, the disable-export switch, and the wiring locations.

How to use it (the load-bearing rules)

navigator dev up does all the wiring — don't redo it by hand. It applies the lgtm pod, port-forwards Grafana :3000 + OTLP :4317, and writes OTEL_EXPORTER_OTLP_ENDPOINT into .devx/env; a hand-rolled forward of svc/lgtm just fights the one it already runs.
No endpoint, no export. Host web only emits OTLP when .devx/env is sourced (it sets the OTLP endpoint, which flips telemetry::init out of stdout-only mode). Expecting telemetry without it is the usual "nothing shows up."
Verify the cross-service trace, not just the span. The headline check is that a web-initiated workflow and its handler steps share one trace id in Tempo across the Restate boundary; a new trace id on the handler span means W3C propagation broke.
Identifiers and counts, never content — even locally. The standing no-content rule is owned by the [[observability]] skill and doc; don't put a client name/answer/email in a span to "make it findable" in Grafana. Log the id, look the rest up.

Boundaries

The emit-side seam — how to ADD a span/metric/log field and the no-content rule — is [[observability]]; the prod landing (Cloud Trace / Cloud Logging / BigQuery) lives there too. LGTM is KIND-only.
Standing up / tearing down the KIND cluster itself: [[kind-local-dev]]. Booting host web against the deps: [[web-preview]].

이 저장소의 다른 Skills

같은 저장소

create-pr

neon-law-foundation/navigator

Turn a dirty working tree into a clean pull request against `main`: survey every change, group the files into Conventional Commits by blast radius (one concern per commit), run the gate, branch off `main`, capture a visual for any user-visible change, push, and open the PR. Trigger when the user says "/create-pr", "create a PR", "open a pull request", "commit and PR these changes", "group these into commits and ship them", or has a dirty working tree they want landed. Stops at "PR open"; building images and deploying to prod is a separate flow.

2026-07-174

rust

neon-law-foundation/navigator

Workspace Rust guardrails. Trigger on the sharpest moments: a change that adds `unsafe`, `unwrap`, `expect`, or `panic!` outside `main()`/tests; introducing a new public API, error type, or module; reaching for a different web framework, ORM, or async runtime (we standardize on Axum + SeaORM + Tokio); or wiring a new binary's `main()`. Read [`docs/rust-programming.md`](../../../docs/rust-programming.md) before acting — it is the authoritative reference.

2026-07-174

pr-image-upload

neon-law-foundation/navigator

Embed a local screenshot or GIF into a GitHub PR (or issue) body so it actually RENDERS on github.com, driven from the CLI — no drag-drop, no committing the file, no image-hosting branch, no release/tag. It uploads the `/tmp` capture to GitHub's native `user-attachments` CDN via the `gh-image` extension (which borrows your logged-in github.com browser session) and returns a real `https://github.com/user-attachments/assets/…` URL to drop into the body. Trigger as the embed half of [[create-pr]] Step 6 (after [[web-preview]] captures the visual), when a reviewer comment on a PR asks for a "live walkthrough"/screenshot during [[review-pr]], or any time you have a `/tmp` image that must appear in a PR/issue body or comment. This is the LOCAL/`gh` path for hosting and embedding a capture. Capture lives in [[web-preview]] — a walkthrough defaults to a GIF of the real interaction (§5), a still (§3) only for a genuinely static change; this skill only hosts + embeds it.

2026-07-164

web-preview

neon-law-foundation/navigator

Run the `web` app locally against the KIND dependency stack and look at it in a real browser — the canonical "spin up web, drive Chrome, capture to /tmp, verify" loop. Trigger whenever asked to run, preview, screenshot, or visually verify `web` / a page / a UI change, to "open the design page", "check it in chrome", or to prove a front-end behavior (syntax highlighting, a toast, a layout, a keyboard shortcut) actually renders. A PR walkthrough defaults to a GIF of the real interaction (§5); a still is only for a genuinely static change. This is the browser half of the local loop; `kind-local-dev` is the cluster half it builds on. Skip for pure logic/unit work — `cargo test` uses testcontainers and needs no cluster.

2026-07-164

kind-local-dev

neon-law-foundation/navigator

Local Kubernetes-in-Docker (KIND) workflow for the navigator workspace — cluster lifecycle, ingress, port-forwarding, the "host runs `web`, deps run in cluster" iteration pattern via the `navigator` CLI. Trigger when running any `navigator` orchestration subcommand (`dev up`, `dev down`, `dev deploy`, `dev kind up`, `dev kind down`, `dev e2e`, `dev logs`, `dev worktree-env`), editing `k8s/kind-config.yaml`, debugging an in-cluster service from the host, or onboarding the cluster from a fresh machine. Also trigger before installing a different local-Kubernetes flavor — we standardize on KIND. Also trigger before proposing to run, preview, screenshot, or manually exercise the app, or before any action that runs on the user's machine (cluster, browser, or cloud commands) — those resolve to this KIND loop, and the move is to propose the commands for the user to run.

2026-07-164

review-pr

neon-law-foundation/navigator

Address a requested pull-request comment against the real code at the PR head. Read the thread, source, and covering test; reproduce behavioral claims in the right KIND-backed environment; apply only the minimum valid fix; prove it; then reply and resolve that thread. Trigger when the user asks to address or review a PR comment, a Greptile finding, or a named review thread. For a request covering several comments, repeat this narrow action for each one without combining their scopes.

2026-07-164

name

grafana-lgtm

description

Seeing telemetry locally with Grafana LGTM

How to use it (the load-bearing rules)

navigator dev up does all the wiring — don't redo it by hand. It applies the lgtm pod, port-forwards Grafana :3000 + OTLP :4317, and writes OTEL_EXPORTER_OTLP_ENDPOINT into .devx/env; a hand-rolled forward of svc/lgtm just fights the one it already runs.
No endpoint, no export. Host web only emits OTLP when .devx/env is sourced (it sets the OTLP endpoint, which flips telemetry::init out of stdout-only mode). Expecting telemetry without it is the usual "nothing shows up."
Verify the cross-service trace, not just the span. The headline check is that a web-initiated workflow and its handler steps share one trace id in Tempo across the Restate boundary; a new trace id on the handler span means W3C propagation broke.
Identifiers and counts, never content — even locally. The standing no-content rule is owned by the [[observability]] skill and doc; don't put a client name/answer/email in a span to "make it findable" in Grafana. Log the id, look the rest up.

Boundaries

The emit-side seam — how to ADD a span/metric/log field and the no-content rule — is [[observability]]; the prod landing (Cloud Trace / Cloud Logging / BigQuery) lives there too. LGTM is KIND-only.
Standing up / tearing down the KIND cluster itself: [[kind-local-dev]]. Booting host web against the deps: [[web-preview]].