Skip to content
LogHouse

Integrations

Datadog stays. The expensive log stream does not have to.

LogHouse stores Datadog API credentials and attempts Federated Logs provisioning when Datadog exposes those APIs. If federation is unavailable—as it often is while that product is in preview—use Observability Pipelines or OpenTelemetry to route logs. The console never marks Datadog connected unless the API actually succeeds.

Applications send telemetry to LogHouse. From LogHouse, data can be used in Datadog, LogHouse Search, and Grafana. Datadog remains in the stack.
Applications
services, clusters, pipelines
LogHouse
economical log backend
↘ Datadog
monitors & workflows
↘ LogHouse Search
high-volume history
↘ Grafana
existing dashboards

Datadog remains part of the stack. LogHouse changes the economics underneath it.

For the cost-focused landing page, see Reduce Datadog log costs.

FAQ

Does this always enable Federated Logs?

No. Federated Logs availability depends on Datadog. LogHouse probes documented APIs and falls back to manual pipeline setup. We do not claim a live federated connection unless Datadog accepts it.

Send us the logs. We'll handle the database.

Send us the logs. We'll handle the database.

Start freeBook a demo

No infrastructure to manage.