AWS Marketplace,Try Free with AWS
Skip to main content

DATABEND SOLUTIONS · USE CASE

Observability

Connect telemetry to business impact

Store logs, traces, and metrics alongside business data. Investigate requests with SQL and connect technical failures to the orders they affect.

From application signals to an explainable impact

A custom OTel Collector exports telemetry into SQL tables. Join signals by trace ID, then add business context.

Architecture: From OpenTelemetry to Business Impact

Scroll horizontally to explore the full diagram.

Architecture: From OpenTelemetry to Business ImpactInstrumented services send OTLP through a custom Collector with the Databend exporter. Streaming Load writes logs, traces, and metrics to separate tables, preserving complete records in VARIANT. SQL correlates telemetry, and order records provide business context for impact analysis.INSTRUMENTED SERVICESDATA APPLICATIONSApplicationsOTel SDKs · OTLPCollectorCustom buildDatabend exporterotel_logsLog records + trace_idFull OTLP in VARIANTotel_tracesSpans + identifiersFull OTLP in VARIANTotel_metricsMetric data pointsFull OTLP in VARIANTSQL analysisCorrelate by trace_idLatency + error countsImpact queriesJoin request contextCalculate affected valueordersBusiness recordsCorrelated order IDsDebug requestsLatency analysisOrder impactGrafana / BINative HTTP Streaming Load · Full OTLP recordsIndependent query and ingestion compute

Preserve full telemetry

Keep complete OTLP payloads in VARIANT alongside typed timestamps and identifiers.

Connect the signals

Correlate logs and spans, calculate latency, and join requests to business records.

Query with familiar tools

Use Worksheet, BendSQL, Grafana, or BI on independent analytical compute.

Explore the details

Ask more of your telemetry

Bring logs, traces, and business data into one SQL investigation.

732 S 6TH ST, STE R, Las Vegas, NV 89101, USA
SOC 2 Type IIGDPR
© 2026 Databend Cloud. All Rights Reserved.