OpenTelemetry Observability

OpenTelemetry access and observability solution

Access OpenTelemetry, OTel Collector, and OTLP data to unify analysis of metrics, logs, traces, profiles, and fault context within the Guance, preserving open standards and reducing vendor lock-in risk.

Get started Request a demo

Why integrate OpenTelemetry data into a unified observability system?

01Maintain open standards

Collect metrics, logs, and traces based on OpenTelemetry to reduce vendor lock-in and transformation costs.

02Unified context analysis

Analyze OTel data by linking it with hosts, containers, logs, RUM, and alert events to form a complete observability view.

03Suitable for multilingual services

Covers multilingual applications and microservices architectures including Java, Go, Python, and Node.js.

04Reduce self-built maintenance

Combining standardized collection with platform analysis capabilities reduces backend storage, querying, alerting, and data pipeline maintenance costs.

05Support migration and expansion

Teams with OTel Collector or SDK can smoothly integrate into a unified observability system.

Access OpenTelemetry Metrics, Logs, and Traces

Guance supports integrating data generated by OpenTelemetry SDK, OTel Collector, or OTLP-compatible protocols into a unified observability system, helping teams gain metrics, logs, traces, profiles, and alert analysis capabilities while retaining open collection standards.
Request a demo
Access OpenTelemetry Metrics, Logs, and Traces
From Trace to services, logs, and infrastructure

From Trace to services, logs, and infrastructure

A slow request can continue to be associated with service topology, error logs, hosts, containers, and dependencies, reducing the problem of only seeing traces without running context.
Request a demo

Unified labels and data calibers for multiple teams

By unifying tags and object relationships, OTel data from different languages, teams, and services can be organized into searchable, alertable, and collaborative analytical views, reducing the risk of subsequent migration and vendor lock-in.
Request a demo
Unified labels and data calibers for multiple teams
OTel data is undertaken through dashboards, monitors, and a closed loop of events

OTel data is undertaken through dashboards, monitors, and a closed loop of events

The data after integration can be used for dashboards, DQL queries, anomaly detection, monitoring alerts, event handling, and review, allowing open standard data to truly enter daily troubleshooting processes rather than just being at the collection layer.
Request a demo

Used together with full-stack observability

OpenTelemetry data can continue to be integrated with RUM, CI, infrastructure, Kubernetes, log governance, and security data to help teams understand the entire system behavior.
Request a demo
Used together with full-stack observability

More technology stacks

Kubernetes Monitoring

Kubernetes Monitoring

 AWS monitoring

AWS monitoring

 Alibaba Cloud Monitoring

Alibaba Cloud Monitoring

 Azure Monitoring

Azure Monitoring

 Huawei Cloud Monitoring

Huawei Cloud Monitoring

Frequently Asked Questions

Can OpenTelemetry data be directly integrated into Guance?

Yes, you can. Teams can collect Metrics, Logs, and Traces data based on OpenTelemetry SDK, OTel Collector, or OTLP-compatible protocols, then integrate them for unified analysis Guance.

Do you already need DataKit if you already have OTel Collector?

It depends on the access method. DataKit can serve as an entry point for Guance data collection and processing, or in conjunction with existing OpenTelemetry acquisition links.

What is the relationship between OpenTelemetry and APM?

OpenTelemetry addresses the issue of data collection standards, while APM focuses more on service performance analysis, link tracing, mislocation, and alert collaboration. Guance combine the two.

Want to know how Guance inherit OpenTelemetry data and integrate full-stack context?

Request a demo

Next steps

Get started > View documentation > View pricing >