Data Integration / 650+ Integrations
Connect 650+ technologies to one observability context
Move from ready-to-use templates and open standards to custom collection, while keeping metrics, logs, traces, RUM, events, and alerts connected by consistent tags and time context.
650+ connected technologies
650+ Guance integrations
Collect
DataKit OpenTelemetry Prometheus Telegraf
Observe
Metrics Logs Traces RUM Events
Connect
Kubernetes AWS Docker MySQL Redis Kafka
Data Integration
Bring a fragmented technology stack into one observability context
Guance uses DataKit, OpenTelemetry, Prometheus, Telegraf, cloud-provider APIs, and custom collection to bring telemetry from hosts, containers, applications, middleware, databases, networks, and cloud platforms into one observability workspace.
650+ integration templates for widely used technologies and cloud services
Unified collection across hosts, containers, Kubernetes, cloud platforms, databases, middleware, networks, logs, and applications
Compatibility with OpenTelemetry, Prometheus, Telegraf, and existing collection ecosystems
Consistent tags, entity relationships, and time context across metrics, logs, traces, RUM, and alerts
Support for custom collection targets and third-party collectors
Cloud-native and infrastructure
Collect host, container, Kubernetes, cloud-resource, network-device, and operating-system data to assess health, capacity risk, and the scope of an incident.
Applications, traces, and logs
Connect application performance, traces, profiles, service logs, and error context so a slow request can be investigated alongside code, dependencies, logs, and resource changes.
Databases, middleware, and cloud services
Cover databases, caches, message queues, gateways, load balancers, and major cloud services without manually stitching evidence together across separate tools.
Implementation path
A practical way to roll out integrations
01Connect critical systems first
Start with the hosts, Kubernetes environments, applications, databases, middleware, and logs behind critical services so recurring failures have a shared evidence base.
02Standardize tags and entities
Align service, environment, version, region, team, and business tags during collection to reduce manual reconciliation later.
03Correlate data in one platform
Place metrics, logs, traces, RUM, events, and alerts on the same time and entity context to explain latency, errors, resource pressure, and business impact.
FAQ
Questions about Guance data integrations
Which technologies do the 650+ Guance integrations cover?
The catalogue covers hosts, containers, Kubernetes, cloud platforms, databases, middleware, networks, logs, applications, Real User Monitoring, and selected business systems. Teams choose the documented integration that matches each technology and collection path.
How does DataKit relate to OpenTelemetry, Prometheus, and Telegraf?
DataKit is the Guance collection Agent. It can collect supported telemetry directly and accept data from OpenTelemetry, Prometheus, Telegraf, and other documented sources, allowing teams to retain useful parts of an existing collection strategy.
Can Guance ingest telemetry from an internal or custom system?
Yes. In addition to packaged integrations, Guance supports documented custom collection, APIs, Pipeline processing, and third-party collectors. The available fields and setup depend on the chosen collection method.
How do teams avoid creating new silos after adding many integrations?
Standardize service, environment, version, region, team, and business tags during collection, then use entity and time context to connect metrics, logs, traces, RUM, events, and alerts during investigation.
