Hosting on Azure Issue

[maulikbahri]

Describe your question

Stuck with Database Resource Limit Exceeded Error
Seeing tRPC error in the logs can't figure out the issue certainly
Issues with clickhouse container buat on the monitor i see no limit has reached no where even close to max cap of container
Additionally i see the records on the storage account just not on the web

Langfuse Cloud or Self-Hosted?

Self-Hosted

If self-hosted, what version are you running?

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[inkeep-ai-assistant[bot]]

Based on your description, you're experiencing a "Database Resource Limit Exceeded" error with records appearing in storage but not in the web UI. This is a known issue pattern in self-hosted Langfuse deployments.(1)

Common causes for this issue:

1. Missing events after ingestion - Events may be successfully stored in S3/blob storage but not appearing in ClickHouse or the UI. This can occur when the worker container isn't properly processing the ingestion queue.(1)

2. ClickHouse connection issues - The web container may be having intermittent connectivity problems with ClickHouse, even if ClickHouse itself isn't hitting resource limits.(1)

3. PostgreSQL table ownership issues - Migration failures can occur if table ownership isn't properly configured, preventing data from being read correctly.(1)

Troubleshooting steps:

1. Check your worker container logs specifically - the worker is responsible for processing events from storage into ClickHouse
2. Verify ClickHouse connectivity from the web container
3. Review PostgreSQL table ownership and permissions
4. Check if background migrations are stuck in "Queued" status(1)

For Azure-specific deployments, there are several documented configuration issues related to SSO and connectivity.(1)

The Troubleshooting & FAQ page(1) contains multiple discussions about similar issues including "Missing events after POST /api/public/ingestion"(1) and "Web to Clickhouse connection issue"(1) that may provide additional context.

Could you share:

• Your specific Langfuse version
• Worker container logs
• Any error messages from the web container about ClickHouse connections

This will help narrow down the exact issue.

📚 Sources:

1. Troubleshooting & FAQ

---

Have another question? Just tag @inkeep.

[jannikmaierhoefer]

Hi @maulikbahri, was inkeep able to help you here?

[maulikbahri]

Nope my issue still exists

…

On Tue, Nov 25, 2025, 2:32 PM Jannik Maierhöfer ***@***.***> wrote: Hi @maulikbahri <https://github.com/maulikbahri>, was inkeep able to help you here? — Reply to this email directly, view it on GitHub <#10675 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AREA4V6F2ARZPZOFKWFG6DD36QLIVAVCNFSM6AAAAACNBPDDVWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBXGIYTKMQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jannikmaierhoefer]

Can you share the tRPC error in the logs you are observing?

[maulikbahri]

Hey Jannik, first of all thanks so much for helping will share error trace Errors on Langfuse-worker container when we ingest a trace within 60 seconds 1. {"TimeStamp": "2025-11-25T13:20:41.79085", "Log": "Connecting to the container 'langfuse-worker-container'..."} {"TimeStamp": "2025-11-25T13:20:42.48923", "Log": "Successfully Connected to container: 'langfuse-worker-container' [Revision: 'langfuse-worker--0000013', Replica: 'langfuse-worker--0000013-8649c7d97c-btrsf']"} {"TimeStamp": "2025-11-25T13:20:40.5131588+00:00", "Log": "F at listOnTimeout (node:internal/timers:608:17)"} {"TimeStamp": "2025-11-25T13:20:40.51316+00:00", "Log": "F at process.processTimers (node:internal/timers:543:7)"} {"TimeStamp": "2025-11-25T13:20:40.5175241+00:00", "Log": "F 2025-11-25T13:20:40.517Z error \tQueue job otel-ingestion-job with id 8 in otel-ingestion-queue failed Timeout error."} {"TimeStamp": "2025-11-25T13:20:40.517557+00:00", "Log": "F Error: Timeout error."} {"TimeStamp": "2025-11-25T13:20:40.5175701+00:00", "Log": "F at Socket.onTimeout ***@***.******@***.******@***.***/client/dist/connection/node_base_connection.js:588:68)"} {"TimeStamp": "2025-11-25T13:20:40.5175739+00:00", "Log": "F at Object.onceWrapper (node:events:622:28)"} {"TimeStamp": "2025-11-25T13:20:40.5175763+00:00", "Log": "F at Socket.emit (node:events:520:35)"} {"TimeStamp": "2025-11-25T13:20:40.5175785+00:00", "Log": "F at Socket._onTimeout (node:net:604:8)"} {"TimeStamp": "2025-11-25T13:20:40.5175926+00:00", "Log": "F at listOnTimeout (node:internal/timers:608:17)"} {"TimeStamp": "2025-11-25T13:20:40.5175953+00:00", "Log": "F at process.processTimers (node:internal/timers:543:7)"} {"TimeStamp": "2025-11-25T13:20:41.4965591+00:00", "Log": "F 2025-11-25T13:20:41.496Z error \tClickhouseWriter.writeToClickhouse Error: Timeout error."} 2. {"TimeStamp": "2025-11-25T13:20:41.4970143+00:00", "Log": "F 2025-11-25T13:20:41.496Z error \tClickHouse query failed with non-retryable error: Timeout error."} {"TimeStamp": "2025-11-25T13:20:41.4972022+00:00", "Log": "F 2025-11-25T13:20:41.497Z error \tClickhouseWriter.flush blob_storage_file_log Timeout error."} {"TimeStamp": "2025-11-25T13:20:41.4972304+00:00", "Log": "F Error: Timeout error."} {"TimeStamp": "2025-11-25T13:20:41.4972429+00:00", "Log": "F at Socket.onTimeout ***@***.******@***.******@***.***/client/dist/connection/node_base_connection.js:588:68)"} {"TimeStamp": "2025-11-25T13:20:41.497246+00:00", "Log": "F at Object.onceWrapper (node:events:622:28)"} {"TimeStamp": "2025-11-25T13:20:41.497253+00:00", "Log": "F at Socket.emit (node:events:520:35)"} {"TimeStamp": "2025-11-25T13:20:41.4972553+00:00", "Log": "F at Socket._onTimeout (node:net:604:8)"} {"TimeStamp": "2025-11-25T13:20:41.4972574+00:00", "Log": "F at listOnTimeout (node:internal/timers:608:17)"} {"TimeStamp": "2025-11-25T13:20:41.4972594+00:00", "Log": "F at process.processTimers (node:internal/timers:543:7)"} Error on Langfuse Web whenever we do ui page load 1. "TimeStamp": "2025-11-25T06:26:31.2658775+00:00", "Log": "F 2025-11-25T06:26:31.265Z error \ttRPC route failed on traces.filterOptions: Database resource limit exceeded. Please use more specific filters or a shorter time range. We are continuously improving our API performance. Database resource limit exceeded. Please use more specific filters or a shorter time range. We are continuously improving our API performance."} {"TimeStamp": "2025-11-25T06:26:31.265897+00:00", "Log": "F TRPCError: Database resource limit exceeded. Please use more specific filters or a shorter time range. We are continuously improving our API performance."} {"TimeStamp": "2025-11-25T06:26:31.2670396+00:00", "Log": "F 2025-11-25T06:26:31.266Z error \tClickHouse query failed with non-retryable error: Timeout error."}

…

On Tue, Nov 25, 2025 at 3:03 PM Jannik Maierhöfer ***@***.***> wrote: Can you share the tRPC error in the logs you are observing? — Reply to this email directly, view it on GitHub <#10675 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AREA4V3DOCDFUHA3HZOZSQD36QO5VAVCNFSM6AAAAACNBPDDVWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBXGI2DOOI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Steffen911]

@maulikbahri How did you setup clickhouse and what's the underlying storage? What's the CPU and memory allocation for the clickhouse containers?