yjIdZddlZddlmZmZmZmZmZmZddl m Z m Z m Z ddl mZmZddlmZddlmZddlmZmZdd lmZmZmZmZdd lmZmZdd lm Z ej!e"Z#gd Z$d eddfdZ%ddZ&ddZ'dS)a CloudEvents telemetry event system for Honcho. This module provides: - emit(): Queue an event for emission to the telemetry backend - BaseEvent: Base class for all event types - Concrete event types for all Honcho operations Event Categories: representation: Message processing and conclusion extraction - RepresentationCompletedEvent: Message batch processed, conclusions extracted dream: Memory consolidation operations - DreamRunEvent: Full dream orchestration completed - DreamSpecialistEvent: Individual specialist (deduction/induction) completed dialectic: User-initiated queries - DialecticCompletedEvent: Chat query completed agent: Agentic loop tracking (correlates via run_id) - AgentIterationEvent: Per-LLM-call metrics - AgentToolConclusionsCreatedEvent: Conclusions created by agent - AgentToolConclusionsDeletedEvent: Conclusions deleted by agent - AgentToolPeerCardUpdatedEvent: Peer card updated by agent - AgentToolSummaryCreatedEvent: Summary created api: User-facing API operations - MessageCreatedEvent: Message batch created - FileUploadedEvent: File converted into messages - GetContextEvent: Context retrieved for a session or peer deletion: Resource removal - DeletionCompletedEvent: Resource deletion completed (with cascade counts) reconciliation: Maintenance operations - SyncVectorsCompletedEvent: Vector store sync completed - CleanupStaleItemsCompletedEvent: Stale items cleanup completed Usage: from src.telemetry.events import emit, RepresentationCompletedEvent emit(RepresentationCompletedEvent( workspace_name="my_workspace", session_name="my_session", observed="assistant_peer", queue_items_processed=3, earliest_message_id="msg_001", latest_message_id="msg_010", message_count=10, explicit_conclusion_count=5, context_preparation_ms=50.0, llm_call_ms=1200.0, total_duration_ms=1300.0, input_tokens=5000, output_tokens=500, )) N)AgentIterationEventAgentToolCallCompletedEvent AgentToolConclusionsCreatedEvent AgentToolConclusionsDeletedEventAgentToolPeerCardUpdatedEventAgentToolSummaryCreatedEvent)FileUploadedEventGetContextEventMessageCreatedEvent) BaseEventgenerate_event_id)DeletionCompletedEvent)DialecticCompletedEvent) DreamRunEventDreamSpecialistEvent) CallPurposeEmbeddingCallCompletedEventEmbeddingCallPurposeLLMCallCompletedEvent)CleanupStaleItemsCompletedEventSyncVectorsCompletedEvent)RepresentationCompletedEvent)emitr r rrrrrrrrrrr r r rrrrrrrinitialize_telemetry_eventsshutdown_telemetry_eventseventreturncf ddlm}|}|tddS||dS#t $r_}ddl}||tdt|j t|Yd}~dSd}~wwxYw)aDQueue an event for emission to the telemetry backend. This is the main entry point for emitting telemetry events. Events are buffered and sent asynchronously to the configured endpoint. If telemetry is disabled or not initialized, this is a no-op. Telemetry failures are caught and logged to Sentry to avoid blocking operations. Args: event: The event to emit (must be a BaseEvent subclass instance) Example: from src.telemetry.events import emit emit(MyEvent( my_field="some_value", ... )) r) get_emitterNz1Telemetry emitter not initialized, dropping eventz%Failed to emit telemetry event %s: %s) src.telemetry.emitterrloggerdebugr Exception sentry_sdkcapture_exceptionwarningtype__name__str)rremitterer$s E/DATA/AppData/hermes/projects/honcho/src/telemetry/events/__init__.pyrrs( 555555+-- ? LLL M M M F U     $$Q''' 3 KK FF          s,AA B0AB++B0c zKddlm}ddlm}|jjst ddS||jj|jj |jj |jj |jj |jj |jjdd{Vt d|jjdS) a)Initialize the telemetry events system based on configuration. This should be called once at application startup. It reads configuration from settings and initializes the CloudEvents emitter. This is typically called from initialize_telemetry() in the main telemetry module. r)settings)initialize_emitterzCloudEvents telemetry disabledNT)endpointheaders batch_sizeflush_interval_secondsflush_threshold max_retriesmax_buffer_sizeenabledz/CloudEvents telemetry initialized, endpoint: %s) src.configr.r r/ TELEMETRYENABLEDr!infoENDPOINTHEADERS BATCH_SIZEFLUSH_INTERVAL_SECONDSFLUSH_THRESHOLD MAX_RETRIESMAX_BUFFER_SIZE)r.r/s r,rrs$#####888888   % 4555  #,"*%0'1H *:&2 *:           KK98;M;VcjKddlm}|d{VtddS)zShutdown the telemetry events system. This should be called during application shutdown to ensure all buffered events are flushed before exit. rshutdown_emitterNz'CloudEvents telemetry shutdown complete)r rFr!r;rEs r,rrsT 766666     KK9:::::rC)rN)(__doc__loggingsrc.telemetry.events.agentrrrrrrsrc.telemetry.events.apir r r src.telemetry.events.baser r src.telemetry.events.deletionrsrc.telemetry.events.dialecticrsrc.telemetry.events.dreamrrsrc.telemetry.events.llmrrrr#src.telemetry.events.reconciliationrr#src.telemetry.events.representationr getLoggerr(r!__all__rrrrCr,rUs88t CBBBBBBB@@@@@@BBBBBB MLLLLL  8 $ $$ $ $ N& & d& & & & R@ ; ; ; ; ; ;rC