Sending Data to KloudMate
KloudMate provides multiple, flexible methods for ingesting your observability data. Because KloudMate is built natively on OpenTelemetry standards, you are never locked into a proprietary collection method.
Choose the ingestion path below that best matches your existing architecture, your environment (cloud vs. on-premise), and how much control you want over the telemetry collection process.
Recommended Starting Points
Section titled “Recommended Starting Points”- Use the KloudMate Agent if you want the fastest path for infrastructure, logs, traces, and zero-code visibility using eBPF.
- Use the OpenTelemetry Collector if you already run OTel and want to keep your existing telemetry pipelines intact.
- Use the AWS or Azure integrations if you want to onboard cloud platform telemetry without instrumenting every workload directly.
- Use the Prometheus integration when your metrics already exist in Prometheus and you want to forward them into KloudMate.
Choose Your Path
Section titled “Choose Your Path” KloudMate Agent Best default for most teams. Install one agent to collect infrastructure telemetry, logs, traces, and eBPF-powered observability.
OpenTelemetry Collector Use this when you already run OpenTelemetry and want to export telemetry to KloudMate without changing your collector-first architecture.
Prometheus Integration Use this when your metrics already live in Prometheus and you want KloudMate to ingest them through an OpenTelemetry-based path.
AWS Integration Use AWS integration guides for account onboarding and service-specific observability such as Lambda monitoring.
Azure Integration Use Azure Monitor and Event Hub integrations to bring Azure platform telemetry into KloudMate.
How to Decide
Section titled “How to Decide”If you are unsure where to begin, use this table to map your immediate goal to the correct starting point.
| If your goal is… | Start here |
|---|---|
| Fastest overall onboarding | KloudMate Agent |
| Reuse existing OTel pipelines | OpenTelemetry Collector |
| Import Prometheus metrics | Prometheus Integration |
| Onboard AWS with minimal setup | AWS Integration |
| Onboard Azure services | Azure Integration |
Common Rollout Pattern
Section titled “Common Rollout Pattern”For teams starting from scratch, we recommend this phased approach:
- Infrastructure First: Start with the KloudMate Agent to get baseline telemetry, host metrics, and zero-code visibility.
- Application Tracing: Add OpenTelemetry instrumentation to your applications where you need richer distributed tracing or custom metrics.
- Cloud Integrations: Layer in cloud-specific integrations for AWS, Azure, or Prometheus to centralize your remaining data sources.