菜单
SignalDB Tempo API compatibility - implemented/stub endpoints, query flow, admin API, Grafana native plugin, and built-in Tempo datasource support. Use when working with HTTP API, Grafana integration, or query endpoints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
SignalDB architecture reference - FDAP stack, write/query data flow, service components, deployment models, and dual catalog system. Use when understanding how components fit together, data flow, or system design.
SignalDB crate map - workspace members, module locations within common/writer/querier/router crates, and key root files. Use when navigating the codebase, finding where code lives, or understanding module boundaries.
SignalDB multi-tenancy and authentication - tenant model, auth flow, isolation layers, slug-based naming, API keys, admin API, and CLI. Use when working with tenant isolation, authentication, API keys, or dataset management.
SignalDB configuration reference - all TOML sections, environment variables, database/discovery/storage/WAL/schema/auth/queue settings, and service ports. Use when working with configuration, environment variables, or TOML settings.
Step-by-step guide for adding a new signal type or table to SignalDB - schema definition, Flight schema, OTLP conversion, WAL operation, acceptor/writer/querier/router updates, and testing. Use when adding new signal types, metric types, or tables.
SignalDB development workflow - build, test, lint, format, run services, Docker, Grafana plugin, health checks, and semantic commits. Use when building, testing, running, or deploying SignalDB.
| name | tempo-api |
| description | SignalDB Tempo API compatibility - implemented/stub endpoints, query flow, admin API, Grafana native plugin, and built-in Tempo datasource support. Use when working with HTTP API, Grafana integration, or query endpoints. |
| user-invocable | false |
| sources | ["src/router/src/endpoints/tempo.rs","src/router/src/endpoints/admin.rs","src/grafana-plugin/src/**","src/grafana-plugin/backend/src/**"] |
| Endpoint | Status | Description |
|---|---|---|
GET /tempo/api/echo | Implemented | Health check |
GET /tempo/api/traces/{trace_id} | Implemented | Single trace lookup -> routes to Querier; start/end time hints prune the scanned range |
GET /tempo/api/v2/traces/{trace_id} | Implemented | Same handler as v1 for now |
GET /tempo/api/search | Implemented | Trace search with filters -> routes to Querier; spss caps spans per span set in the response |
GET /tempo/api/search/tags | Implemented | Static tag set of actually-queryable tags (service.name, name, status) |
GET /tempo/api/search/tag/{tag_name}/values | Implemented | Real data: distinct column values via Flight SQL for supported tags; static values for status; 501 for unindexed attribute tags |
GET /tempo/api/v2/search/tags | Implemented | Same tag set, scoped (resource/intrinsic) |
GET /tempo/api/v2/search/tag/{tag_name}/values | Implemented | Same backing as v1 tag values |
GET /tempo/api/metrics/query | 501 Not Implemented | TraceQL metrics not implemented (returns 501 since #552, no fabricated series) |
GET /tempo/api/metrics/query_range | 501 Not Implemented | Same as above |
QueryExecution capabilitydo_get ticket to Querierfind_trace:{tenant_slug}:{dataset_slug}:{trace_id}[:{start}:{end}] (unix-second time hints, appended only when present) or search_traces:{tenant_slug}:{dataset_slug}:{params}not_found status -> HTTP 404)The standalone querier serves Tempo's internal tempopb.Querier gRPC
protocol on its Flight port (default :50054) so a Tempo query-frontend can
use SignalDB as a querier (src/querier/src/services/tempo.rs):
FindTraceByID / SearchRecent: implemented, backed by TraceServiceTenantContext extension wins, else X-Scope-OrgID
header (dataset default), else default/defaultSearchBlock: Unimplemented (no Tempo block model in SignalDB)Requires admin_api_key from config:
| Endpoint | Method | Description |
|---|---|---|
/api/v1/admin/tenants | GET/POST | List/create tenants |
/api/v1/admin/tenants/{id} | GET/PUT/DELETE | Manage tenant |
/api/v1/admin/tenants/{id}/api-keys | GET/POST | List/create API keys |
/api/v1/admin/tenants/{id}/api-keys/{key_id} | DELETE | Revoke API key |
/api/v1/admin/tenants/{id}/datasets | GET/POST | List/create datasets |
/api/v1/admin/tenants/{id}/datasets/{dataset_id} | DELETE | Delete dataset |
A separate tenant self-service API is mounted at /api/v1 (see the
multi-tenancy skill).
src/grafana-plugin/)@grafana/data, @grafana/ui)grafana-plugin-sdk, connects to Router's Flight service (default http://localhost:50053); standalone cargo workspace (own lockfile/target), built via npm run build:backendThe Router's Tempo-compatible endpoints at /tempo/api/... work directly with Grafana's Tempo datasource for trace lookup and basic search.
| File | Purpose |
|---|---|
src/router/src/endpoints/tempo.rs | Tempo API HTTP handlers |
src/router/src/endpoints/admin.rs | Admin API handlers |
src/tempo-api/ | Protobuf definitions and Tempo types |
src/querier/src/flight.rs | Query execution, ticket parsing |
src/grafana-plugin/ | Native Grafana plugin |