Run any Skill in Manus with one click

query-telemetry

Stars105

Forks17

UpdatedJune 18, 2026 at 04:22

Query the {{ProductName}} observability stack (OTLP → Grafana/Loki/Tempo/Prometheus) for logs, traces, and metrics during diagnosis. Use when investigating an issue via telemetry — errors, latency, request traces, custom metrics. Preloaded by the rca-investigator agent.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

atherio-danp

atherio-danp/cde-dotnetcc

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	query-telemetry
description	Query the {{ProductName}} observability stack (OTLP → Grafana/Loki/Tempo/Prometheus) for logs, traces, and metrics during diagnosis. Use when investigating an issue via telemetry — errors, latency, request traces, custom metrics. Preloaded by the rca-investigator agent.
argument-hint	<environment> <query>
allowed-tools	Read, Bash

Query telemetry ({{ProductName}})

Query our self-hosted observability stack to see what actually happened. Queries the OTLP/Grafana stack: Loki (logs, LogQL), Tempo (traces, TraceQL), Prometheus (metrics, PromQL). Telemetry is emitted per the otel-instrumentation skill (sources/meters are {{ProjectName}}.<Feature>).

⚠ Endpoints & auth are PLACEHOLDERS. No observability stack is deployed yet. Fill these in once it exists (your OTLP/Grafana endpoint); until then this is the agreed shape — ask Dan for specifics. Tokens come from env / a vault; never hardcode.

Environment configuration (PLACEHOLDER — fill at deploy)

Environment	Grafana / data-source endpoints	Auth
prod	Loki `<LOKI_URL_PROD>` · Tempo `<TEMPO_URL_PROD>` · Prometheus `<PROM_URL_PROD>`	`<token via env/vault>`
test	`<…_TEST>`	`<token via env/vault>`

Query commands (PLACEHOLDER)

# Logs (LogQL) — e.g. via logcli or the Loki HTTP API:
logcli --addr="$LOKI_URL_PROD" query '{service="{{ProjectName}}-api"} |= "error"' --since=1h -o jsonl
# Metrics (PromQL) — Prometheus HTTP API:
curl -s --get "$PROM_URL_PROD/api/v1/query" --data-urlencode 'query=<PROMQL>'
# Traces (TraceQL) — Tempo HTTP API:
curl -s --get "$TEMPO_URL_PROD/api/search" --data-urlencode 'q=<TRACEQL>'

What's where

Signal	Store / language	Notes
Logs	Loki / LogQL	Structured logs; correlate by `TraceId`/`SpanId` (OTel log correlation).
Traces / spans	Tempo / TraceQL	Spans from `{{ProjectName}}.<Feature>` ActivitySources; HTTP + EF Core auto-instrumentation.
Metrics	Prometheus / PromQL	Counters/histograms from `{{ProjectName}}.<Feature>` meters.

Discipline

All times UTC.
No secrets/PII in telemetry — and don't print any that slipped in; flag it as a finding (it's an A09 issue).
Discover tenants dynamically; never hardcode ids. Be careful with high-cardinality labels.
Quote query results as evidence; correlate logs↔traces↔metrics by trace id.

Steps

Pick the environment ($0, default prod) and signal (logs/traces/metrics).
Run the query against the right store.
Present results cleanly and tie them back to the hypothesis under test.

More from this repository

same repository

add-domain-entity

atherio-danp/cde-dotnetcc

Add a domain entity, aggregate, or value object to the .NET API — rich mutable class with private ctor + static factory (UUIDv7), invariants that throw, tenant_id, identity equality; records for value objects. Use when modeling new domain state under apps/api/{{ProjectName}}.Domain.

2026-06-19105

add-endpoint

atherio-danp/cde-dotnetcc

Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.

2026-06-19105

cqrs-kommand

atherio-danp/cde-dotnetcc

Author a CQRS command or query in the {{ProductName}} backend using the Kommand library, the three-scope validation model, and the Result<T> failure pattern. Use whenever creating or modifying a command/query/handler/validator in apps/api/{{ProjectName}}.Application, or wiring its endpoint in {{ProjectName}}.Api.

2026-06-19105

dotnet-ai-stack

atherio-danp/cde-dotnetcc

Choose and wire AI features in the .NET backend — LLM calls, agentic tool-calling/multi-step workflows, RAG/vector search, structured output, streaming. Use when adding or changing anything that talks to a model or orchestrates agents (your agentic pipeline). Tailored to our LLM provider + MAF + pgvector stack.

2026-06-19105

dotnet-performance-review

atherio-danp/cde-dotnetcc

Scan .NET/C# code for performance anti-patterns (async, memory/strings, collections/LINQ, regex, serialization, I/O) with tiered severity, reporting findings without editing. Use when auditing hot paths, reviewing allocation-heavy code, or analyzing the API for optimization opportunities.

2026-06-19105

efcore-patterns

atherio-danp/cde-dotnetcc

Add or change EF Core (Npgsql/PostgreSQL) persistence in the .NET backend — entities, EF configurations, repositories, queries, migrations. Use when adding a table/entity, a query, a repository, or a migration under apps/api.

2026-06-19105

name	query-telemetry
description	Query the {{ProductName}} observability stack (OTLP → Grafana/Loki/Tempo/Prometheus) for logs, traces, and metrics during diagnosis. Use when investigating an issue via telemetry — errors, latency, request traces, custom metrics. Preloaded by the rca-investigator agent.
argument-hint	<environment> <query>
allowed-tools	Read, Bash

Query telemetry ({{ProductName}})

⚠ Endpoints & auth are PLACEHOLDERS. No observability stack is deployed yet. Fill these in once it exists (your OTLP/Grafana endpoint); until then this is the agreed shape — ask Dan for specifics. Tokens come from env / a vault; never hardcode.

Environment configuration (PLACEHOLDER — fill at deploy)

Environment	Grafana / data-source endpoints	Auth
prod	Loki `<LOKI_URL_PROD>` · Tempo `<TEMPO_URL_PROD>` · Prometheus `<PROM_URL_PROD>`	`<token via env/vault>`
test	`<…_TEST>`	`<token via env/vault>`

Query commands (PLACEHOLDER)

# Logs (LogQL) — e.g. via logcli or the Loki HTTP API:
logcli --addr="$LOKI_URL_PROD" query '{service="{{ProjectName}}-api"} |= "error"' --since=1h -o jsonl
# Metrics (PromQL) — Prometheus HTTP API:
curl -s --get "$PROM_URL_PROD/api/v1/query" --data-urlencode 'query=<PROMQL>'
# Traces (TraceQL) — Tempo HTTP API:
curl -s --get "$TEMPO_URL_PROD/api/search" --data-urlencode 'q=<TRACEQL>'

What's where

Signal	Store / language	Notes
Logs	Loki / LogQL	Structured logs; correlate by `TraceId`/`SpanId` (OTel log correlation).
Traces / spans	Tempo / TraceQL	Spans from `{{ProjectName}}.<Feature>` ActivitySources; HTTP + EF Core auto-instrumentation.
Metrics	Prometheus / PromQL	Counters/histograms from `{{ProjectName}}.<Feature>` meters.

Discipline

All times UTC.
No secrets/PII in telemetry — and don't print any that slipped in; flag it as a finding (it's an A09 issue).
Discover tenants dynamically; never hardcode ids. Be careful with high-cardinality labels.
Quote query results as evidence; correlate logs↔traces↔metrics by trace id.

Steps

Pick the environment ($0, default prod) and signal (logs/traces/metrics).
Run the query against the right store.
Present results cleanly and tie them back to the hypothesis under test.