I have both datadog_token and datadog_region set but i see no logs being forwarded into the datadog instance - is there any open issue here? anything else i have to configure?

Thanks for reaching out, Rohit. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

1. agents are deployed to livekit cloud. 2. yep the secrets can be seen from teh livekit UI. 3. yes i can see the logs. 4. eu.

Thanks — helpful details. Next steps to narrow this down: 1. Check agent logs for forwarding errors — search for “datadog”, “dd-logs”, or any HTTP/connection errors in

lk agent logs --id <agent-id>

. Share any matching error lines you find. 2. Verify the Datadog token has Logs Intake permissions (ingest API key for EU site). Confirm it's not an API key for metrics-only. 3. Confirm region mapping: you set

datadog_region=eu

(correct for Datadog EU). Double-check your Datadog intake endpoint accepts EU keys (e.g.,

http-intake.logs.datadoghq.eu

). 4. Restart the agent deployment after you updated secrets to ensure the runtime picked them up. 5. If you see logs locally but nothing in Datadog, try a simple test log line (e.g.,

log().info("datadog-test")

) and watch for any forwarding errors immediately after. Please paste any Datadog-related error lines from the agent logs and confirmation about the token type/permissions and I’ll give the next specific steps. Sources: Where to find your Agent Logs | LiveKit | Agent deployment overview | LiveKit Documentation | Where to find your Agent Logs | LiveKit, with interactive elements

i did all this - there is literally no error here. also what's surprising is that as i do a call, lk agent logs itself doesn't show me any logs.

Thanks — I hear your frustration. You mentioned no errors and that

lk agent logs

shows nothing during a call. A few clarifications and targeted checks so I can help further: • When you say “lk agent logs itself doesn't show me any logs,” do you see any logs from that agent at all after the call ends? (Agent observability uploads session logs only after a session completes — live session logs may not appear during the call.) • Please share the agent ID you’re testing with so I can look at its runtime status. While you confirm those, please do the following if you haven’t already: 1. After finishing a call, run:

lk agent logs --id <agent-id>

and paste any Datadog-related lines or any lines at all (even timestamps). 2. Add an explicit test log in the agent code before/after the call (e.g.,

log().info("datadog-test-start")

and

log().info("datadog-test-end")

) and check logs after the session ends. 3. Verify agent log level includes INFO/DEBUG so those test lines are emitted. 4. Confirm you restarted the agent after secrets were set (secrets are injected at runtime). 5. Confirm Datadog ingestion: does your Datadog account show any logs from other sources for the

eu

intake? This rules out an account-side ingestion issue. Send the agent ID plus the post-session

lk agent logs

output (or any Datadog-related log lines). Once I have that I’ll give the next specific steps. , with interactive elements