§ y¼jÊãó>—dZddlmZddlmZmZgd¢Zd d„Zd d„ZdS) a÷ Telemetry module for Honcho. This module consolidates all telemetry, metrics, and observability functionality: - Sentry: Error tracking and performance tracing - Prometheus: Pull-based metrics scraped by Fly.io - CloudEvents: Structured events for analytics (push-based) - Logging: Langfuse integration, Rich console output, metric accumulation - Tracing: Sentry transaction decorators - Metrics Collector: JSON file-based benchmark aggregation - Reasoning Traces: JSONL logging of LLM inputs/outputs é)Úemit)Úmetrics_endpointÚprometheus_metrics)rÚinitialize_telemetry_asyncrrÚshutdown_telemetryÚreturnNcƒó^K—ddlm}ddlm}|jjr|¦«ƒd{V—†dSdS)aw Initialize async telemetry systems based on configuration. This should be called once at application startup (in main.py lifespan). It initializes: - CloudEvents emitter (if TELEMETRY_ENABLED=true) Note: Prometheus metrics are pull-based and require no initialization. Sentry is initialized separately in sentry.py as it has its own lifecycle. r)Úsettings)Úinitialize_telemetry_eventsN)Ú src.configr Úsrc.telemetry.eventsr Ú TELEMETRYÚENABLED)r r s ú>/DATA/AppData/hermes/projects/honcho/src/telemetry/__init__.pyrrskèè€ð$Ð#Ð#Ð#Ð#Ð#Ø@Ð@Ð@Ð@Ð@Ð@àÔÔ!ð,Ø)Ð)Ñ+Ô+Ð+Ð+Ð+Ð+Ð+Ð+Ð+Ð+Ð+ð,ð,ócƒó6K—ddlm}|¦«ƒd{V—†dS)zš Shutdown all telemetry systems gracefully. This should be called during application shutdown to ensure: - CloudEvents buffer is flushed r©Úshutdown_telemetry_eventsN)r rrs rrr,sCèè€ð?Ð>Ð>Ð>Ð>Ð>ð $Ð #Ñ %Ô %Ð%Ð%Ð%Ð%Ð%Ð%Ð%Ð%Ð%r)rN) Ú__doc__r rÚsrc.telemetry.prometheusrrÚ__all__rr©rrúrs~ðð ð ð&Ð%Ð%Ð%Ð%Ð%ØIÐIÐIÐIÐIÐIÐIÐIð ð ð €ð,ð,ð,ð,ð$ &ð &ð &ð &ð &ð &r