Skip to content

Conversation

@jjmaldonis
Copy link

Deepgram request IDs are necessary for investigating behavior at the request level. This commit adds DEBUG logs that print Deepgram request IDs when using Deepgram's STT or TTS.

Example log statements:

2025-11-17 12:25:54.894 | DEBUG    | pipecat.services.deepgram.stt:_connect:242 - DeepgramSTTService#0: Websocket connection initialized: {"headers": {'dg-project-id': 'e87380a0-834e-4f9f-b6ac-38324d90fef3', 'dg-request-id': '387b6093-f8f2-410e-b2e1-649033119e76'}}
2025-11-17 12:25:56.114 | DEBUG    | pipecat.services.deepgram.tts:run_tts:122 - DeepgramTTSService#0: HTTP connection initialized: {"headers": {'dg-model-name': 'aura-2-andromeda-en', 'dg-model-uuid': 'd40bb3c8-0122-484c-87db-943c415fb7d9', 'dg-char-count': '6', 'dg-project-id': 'e87380a0-834e-4f9f-b6ac-38324d90fef3', 'dg-request-id': '477b6af6-cfce-41b1-a8b3-9db6f03744b3'}}

Deepgram request IDs are necessary for investigating behavior at the
request level. This commit adds DEBUG logs that print Deepgram request
IDs when using Deepgram's STT or TTS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant