This page maps every signal area synthkit can emit. Each entry links to the authoritative signals/<area>.md source file. For how to read the yaml signals blocks, the verification legend, and the scope/sink concepts, see Reading the Catalogue. For the constructs that emit these signals, see Constructs. For the blueprint declarations that gate which constructs are active, see Emission Switches.
The catalogue is organised into groups below. The Scope column is blueprint (carries a blueprint= selector label) or substrate (disambiguated by declared identity — no blueprint label). The Sink(s) column uses the short identifiers: promrw = Prometheus Remote-Write v2 → Mimir; otlp = hand-encoded OTLP → Tempo; loki = Loki push; faro = Faro collector; pyroscope = Pyroscope push.
AWS CloudWatch metric-stream families: ALB, NLB, EC2, EBS, NAT Gateway, S3, EKS control-plane, Firehose, RDS, ElastiCache, MWAA, DocumentDB, Neptune, OpenSearch Serverless, Glue, PrivateLink. 5-stat gauge expansion (_sum/_average/_maximum/_minimum/_sample_count) per metric. The CW naming convention (aws_<namespace>_<metric>_<stat>) is stated here as LAW and referenced everywhere else.
blueprint
promrw
CloudWatch naming convention
Every _sum-suffixed series is a per-period gauge, not a monotonic counter. Never apply rate() or increase() to any _sum series — use the raw value or delta(). There are no _bucket series on any CW family.
Kubernetes monitoring substrate: KSM (kube_*), node-exporter (node_*), cAdvisor (container_*), kubelet (kubelet_*), conformance/discovery, Kubernetes Events log stream, and add-on pod correlation labels. The k8s-addon-pod-correlation family joins add-on pod identity into the k8s series via shared fixture.PodIP.
Grafana Cloud Database Observability — MySQL (dbo11y_mysql_*) and Postgres (dbo11y_pg_*) metric families plus their matching structured log streams. Substrate-scoped; disambiguated by instance (connection URI), server_id (64-hex SHA-256), and db_instance_identifier. Live-validated against the Grafana Cloud Database Observability product stack. Two independently-gated lanes; both default off; cross-signal join key is the DB Name, which also links to the CSP hosting metrics and trace db-leaf spans.
substrate
promrw + loki
Emission switch
A databases: entry in a blueprint can gate the CloudWatch RDS lane (cloudwatch: true/false) and the dbo11y lane (dbo11y: true/false) independently. Both default to their own values; neither forces the other on.
Cloudflare zone analytics (cloudflare_zone_*) and tunnel metrics (cloudflare_tunnel_*). Unlike the Azure/GCP CSP families, Cloudflare is blueprint-scoped and carries the blueprint selector label.
Distributed traces — one connected span tree per request: browser ROOT → server CLIENT → db/cache leaf spans, plus typed AI hops (gateway/model/agent/tool/workflow/retrieval). Hand-encoded multi-Resource ResourceSpans protobuf delivered via OTLP. Span attributes, resource attributes, and the correlation key-set (app.correlation_id, trace_id, span_id) are defined here. Blueprint-scoped (carried by web_service workload).
OTel gen_ai semantic-convention span attributes and gen_ai_client_* / gen_ai_server_* metric families. Workload-emitted (the web_service AI hops); vocabulary lives in internal/genai. Two core client metrics (gen_ai_client_token_usage, gen_ai_client_operation_duration_seconds) are live-confirmed; streaming families are v: assumed. Labels use gen_ai_provider_name (current OTel spelling; replaces the legacy gen_ai_system).
The per-model LLM catalogue — model IDs, families, cost per 1M input/output tokens, and volume weights for all four platforms: AWS Bedrock, Azure OpenAI, OpenAI, Vertex AI. This is a reference table (mirror of internal/genai/models.go), not an emitted signal family. No scope or sink.
Portkey LLM gateway telemetry: the gateway pods' /metrics scrape (portkey_* + node_*), the Portkey Analytics API poll (portkey_api_* gauges), the export log stream, and derived recording rules. Two constructs share this contract (portkey_gateway and portkey_poller). Substrate-scoped; disambiguated by gateway instance identity.
AWS Bedrock AgentCore CloudWatch families: AWS/Bedrock-AgentCore invocation-class metrics and resource-usage metrics. Plus the AgentCore JSON log stream. Blueprint-scoped; same CW naming convention as other AWS namespaces.
Snowflake account telemetry via Alloy prometheus.exporter.snowflake — 27 gauge families from ACCOUNT_USAGE views. Not a CloudWatch source. Substrate-scoped; disambiguated by Snowflake account identity.
Grafana Beyla eBPF auto-instrumentation: RED metrics (http_server_request_duration_seconds, http_server_request_body_size_bytes, http_client_*), network-flow metrics (beyla_network_flow_bytes_total), span-metric cross-references, and Beyla internal agent metrics. Two contexts: ebpf_only (no SDK) and coexist_sdk (Beyla alongside an OTel SDK). Traces delivered via OTLP. Dual-scoped: RED and span-metric families are blueprint-scoped (emitted via the web_service Beyla lane); network-flow and internal metrics are substrate-scoped.
Native OTLP application metrics emitted by the web_service workload when otel: { metrics: true } is declared. Ships OTel semantic instrument names (http.server.request.duration, http.server.active_requests) via OTLP/HTTP rather than pre-mangled Prometheus RW2. Documents both the emitted OTLP instruments and the expected post-gateway Prometheus shape (http_server_request_duration_seconds, http_server_active_requests, target_info, otel_scope_*) for both naked and k8s_monitoring resource modes. Blueprint-scoped.
GitLab CI qualification and validation pipeline telemetry: the gitlab_ci_pipeline_* family from mvisonneau/gitlab-ci-pipelines-exporter (exporter-doc verified) plus a coined qualification_* suite-signal family for synthkit's own validation pass results. Metric names and label keys confirmed against upstream exporter documentation. Plus a structured Loki log stream. Substrate-scoped; no blueprint label.
The global rules that apply to every area above — push topology, blueprint selector stamping, scope invariants, environment-label-key variance, the correlation key-set, the cardinality hard limit, the content-strip rule, and the realistic-shape model — live in signals/00-canon.md. Area files reference these by slug ([slug: cardinality], [slug: scoping], etc.) and never restate them.