Recommended patterns for reliably sending high-volume telemetry to Axiom using industry-standard collectors like OpenTelemetry and Vector.
k8s.pod.name
, host.id
) and providing a resilient, decentralized collection point with local buffering.
otel-collector-config.yaml
):
AXIOM_DOMAIN
with api.axiom.co
if your organization uses the US region, and with api.eu.axiom.co
if your organization uses the EU region. For more information, see Regions.Replace API_TOKEN
with the Axiom API token you have generated. For added security, store the API token in an environment variable.Replace DATASET_NAME
with the name of the Axiom dataset where you send your data.vector.toml
):
VECTOR_SOURCE_ID
with the Vector source ID.
Replace PATH_TO_LOGS
with the path to the log files. For example, /var/log/**/*.log
.
Replace SINK_ID
with the sink ID.Replace API_TOKEN
with the Axiom API token you have generated. For added security, store the API token in an environment variable.Replace DATASET_NAME
with the name of the Axiom dataset where you send your data.Aspect | OpenTelemetry Collector | Vector |
---|---|---|
Primary Use Case | Unified pipeline for logs, metrics, and traces | High-performance log collection and transformation |
Ecosystem | CNCF and OpenTelemetry standard | Standalone, broad source/sink compatibility |
Transformation | Processors (limited for complex logic) | Vector Remap Language (VRL) for advanced logic |
Performance | Excellent | Excellent, often with lower resource footprint for logs |