Skip to content
Shield360 Shield360 Shield360

Telemetry Sources

Telemetry Sources is the same product surface as Connectors. Prefer the connectors and signal-routing guides below — they match the Shield360 dashboard language (connectors, actions, and per-signal routing).

Connectors

Catalog of supported Shield360 + OpenPlait data-source connectors and actions.

 Signal routing

How traces, logs, and metrics are bound per project and environment.

 Environments

How Database Configs and connectors are partitioned.

 Database Config

ClickHouse app store and how INIT_DB_* env vars became Database Config.

Quick summary

Section titled “Quick summary”

Shield360 reads raw traces, logs, and metrics from the built-in ClickHouse store by default. You can attach external backends supported in Shield360 — Tempo, Loki, Prometheus, and Jaeger — and bind each signal independently per environment. Derived intelligence always stays in ClickHouse via Database Config.

For auth tables, AI selectors, correlation limits, and reliability hardening, see Data-source connectors — that document is the canonical reference for telemetry backends.