Overview
The Telemetry page is the single home for every OpenTelemetry signal Shield360 ingests from your AI applications. Navigate to it at /telemetry. It has four tabs, all backed by the same ClickHouse tables (otel_traces, otel_metrics_*, otel_logs) populated by the OpenTelemetry Collector built into Shield360:
Distributed traces with generation-issue chips, grouping, a five-view detail explorer, and span/resource attributes
AI AnalysisAI-generated review of a trace or span across strengths, improvements, cost, and token efficiency
MetricsEvery OTel metric Shield360 has received, with a trend chart and data-point detail per metric
LogsSearchable, filterable OTel log records with a detail view per entry
The Exceptions tab is documented alongside Traces since it reuses the same trace detail explorer - see Traces & Exceptions.
Production-ready AI monitoring setup in 2 simple steps with zero code changes
Create a dashboardCreate custom visualizations with flexible widgets, queries, and real-time AI monitoring
Integrations60+ AI integrations with automatic instrumentation and performance tracking
Frequently asked questions
Section titled “Frequently asked questions”What is AI observability?
AI observability is the practice of collecting traces, metrics, and logs from LLM applications and agents so you can understand behavior, cost, latency, and errors in production - Shield360 does this via standard OpenTelemetry data.
Does Shield360 support log monitoring, not just traces?
Yes. Logs have their own dedicated explorer under Telemetry, ingested the same way as traces and metrics through the built-in OpenTelemetry Collector’s OTLP receiver.
Can I still use dashboards alongside the Metrics explorer?
Yes. The Metrics explorer and Dashboard Widgets read from the same underlying data - use the explorer to inspect a single metric, and dashboards for cross-signal, trend-style visualizations.