Every pod, node and service.
One DaemonSet, no sidecars.
Cluster health, workload metrics, service-to-service traffic and container logs in one place. Deploy axonIQzerocode once per node, keep your OpenTelemetry Collector and Prometheus scrapes, and see the whole cluster without touching application code.
Deep Dive
Core Capabilities & Architecture
Explore how Kubernetes Monitoring instruments, processes, and correlates high-cardinality telemetry at scale.
One DaemonSet observes the whole cluster
Install axonIQzerocode with Helm, once per node. It discovers running pods, enriches every signal with namespace, deployment, container and node labels, and exports OTLP. No restarts, no sidecars, no SDKs to roll out team by team.
- Helm chart installation with zero cluster restart requirements
- Automatic pod, namespace, container, and node label enrichment
- BPF Type Format (BTF) support across modern Linux kernels (5.4+)
- Namespace exclusion filters and data drop rules
Golden signals for every workload, from the kernel up
Request rate, error rate and P50/P95/P99 latency for every service, reconstructed from socket traffic. HTTP/1.1, HTTP/2, gRPC, PostgreSQL, MySQL and Redis calls are recognised automatically, so even third-party images report.
- Latency, throughput and error status per workload
- Auto-discovered service-to-service map from real connections
- TCP retransmissions, socket drops and connection resets
- Correlates with application OpenTelemetry spans where they exist
Keep your Prometheus scrapes and Collector pipelines
Point Prometheus remote_write or an OpenTelemetry Collector at aiAxonIQ and cluster metrics land beside traces and logs, queryable in PromQL. Nothing about your existing scrape configs has to change.
- Prometheus remote_write and native OTLP metrics ingestion
- PromQL-compatible queries over cluster and node metrics
- Container logs searchable next to the traces that produced them
- Import existing Grafana dashboards via JSON
Built for every team that cares about reliability
One platform, tailored to how your team actually works.
Cluster-wide visibility on day one
See every workload the moment the DaemonSet starts, without asking each team to instrument first.
From a noisy node to the pod behind it
Move from a node-level alert to the workload, the request and the log line without switching tools.
Rollouts you can watch
Compare latency and error rate across a deployment while it rolls out, per namespace and version label.
Kernel signals and open standards, in the same store
axonIQzerocode attaches eBPF probes on each node and exports OTLP. Prometheus and OpenTelemetry Collector pipelines send metrics and logs to the same ingest. Everything streams through Kafka into ClickHouse, so a pod, its traffic and its logs are one query apart.
Also in the platform
Start Kubernetes monitoring in 5 minutes
Your existing OpenTelemetry instrumentation works unchanged, so there is nothing to rewrite and nothing to migrate.