# OpenTelemetry Collector with Telemio

Use an OpenTelemetry Collector when many runtimes need one controlled export path, when clients cannot safely hold a server credential, or when telemetry needs batching, filtering, resource enrichment, sampling, or routing before it reaches Telemio.

## Recommended pipeline

- OTLP receiver over HTTP and/or gRPC
- memory limiter
- resource and attributes processors as needed
- batch processor
- filtering/redaction where policy requires it
- OTLP/HTTP exporter to Telemio
- health check extension

Keep the Telemio server API key in the Collector environment or secret store. Do not bake it into a public image or client application.

Generate a starting configuration with:

```bash
telemio setup collector
```

For Kubernetes use one or more gateway/agent Collectors depending on volume and topology, and enrich telemetry with Kubernetes resource metadata.