service_resilienceTier 1 · 70% confidence

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

agent: infrastructure

When does this happen?

IF ClickHouse is unavailable causing trace ingestion to fail with 500 and data to be permanently lost

How others solved it

THEN Configure Langfuse to use PostgreSQL as the ingestion queue by setting LANGFUSE_INGESTION_QUEUE_TYPE=postgres and set LANGFUSE_INGESTION_QUEUE_MAX_RETRIES=-1 to keep retrying indefinitely. This ensures incoming traces are buffered in PostgreSQL during ClickHouse downtime and processed once ClickHouse recovers, preventing data loss and 500 errors.

LANGFUSE_INGESTION_QUEUE_TYPE=postgres
LANGFUSE_INGESTION_QUEUE_MAX_RETRIES=-1

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%
api_url_encoding

infrastructure-api-url-encoding-api-call-to-retrieve-a-dataset-fails-with-404-when-3d45fd79

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics