Infrastructure Integrations
Osuite collects metrics from databases, message queues, web servers, and cloud platforms through the OpenTelemetry Collector. Each integration adds a receiver for the technology, routes it through the shared otlp/osuite exporter, and the metrics land in Osuite correlated with your traces and logs by resource attributes.
The database, queue, and web-server receivers below ship in the Collector contrib distribution (otelcol-contrib). Point the exporter at your ingest endpoint and the metrics flow with no per-vendor agent.
Available integrations
Section titled “Available integrations”| Technology | Receiver | Signals |
|---|---|---|
| PostgreSQL | postgresql | Metrics |
| MySQL | mysql | Metrics |
| Redis | redis | Metrics |
| MongoDB | mongodb | Metrics |
| Kafka | kafka_metrics | Metrics |
| RabbitMQ | rabbitmq | Metrics |
| NGINX | nginx | Metrics |
| Apache HTTP Server | apache | Metrics |
| HAProxy | haproxy | Metrics |
| Elasticsearch | elasticsearch | Metrics |
| AWS | awscloudwatch | Metrics |
| Google Cloud | googlecloudmonitoring | Metrics |
| Azure | azure_monitor | Metrics |
How integrations work
Section titled “How integrations work”Every integration follows the same shape:
- Grant the Collector read access on the target (a monitoring user, a status endpoint, or a management API).
- Add the receiver to your Collector configuration and wire it into a metrics pipeline alongside the
otlp/osuiteexporter. - Metrics appear in Dashboards → Explore metrics, where you can build dashboards and set PromQL alerts.
The database, queue, and web-server pages use deployment tabs (bare host, Docker, Kubernetes) — every tab is a complete, copy-paste configuration for that target.
Related
Section titled “Related”- Host monitoring — CPU, memory, disk, and network with the
hostmetricsreceiver - Kubernetes monitoring — cluster, node, and pod metrics
- Collect logs — pair these metrics with logs from the same systems