Telemetry¶
Telemetry provides comprehensive observability and monitoring capabilities for QType applications, enabling developers to track performance, debug issues, and gain insights into application behavior. It captures metrics, traces, and logs across all components including steps, flows, model interactions, and tool executions.
Telemetry is essential for production deployments, allowing teams to monitor application health, optimize performance, identify bottlenecks, and troubleshoot issues in real-time or through historical analysis.
Only one telemetry sink can be configured per application. For multiple destinations, use a telemetry aggregator like OpenTelemetry Collector.
Component Definition¶
TelemetrySink¶
Defines an observability endpoint for collecting telemetry data from the QType runtime.
- id (
str): Unique ID of the telemetry sink configuration. - auth (
AuthorizationProvider | str | None): AuthorizationProvider used to authenticate telemetry data transmission. - endpoint (
str): URL endpoint where telemetry data will be sent.
Related Concepts¶
Telemetry observes all QType components including Steps, Flows, Models, Tools, and Memory. It integrates with AuthorizationProvider for secure data export and provides insights for optimizing Variable data flow.