Skip to main content
A running agent is not a working agent. This page is the difference.
Availability. The zero-code agent is an early-access distribution. It is installable, upgradable and tested, and it is not yet an integrated part of the product: there is no dashboard page for it, no in-product installer and no self-service download. Ask your account contact for access.Its telemetry, once flowing, is ordinary OTLP and needs nothing special — it appears in Services, Traces and Metrics exactly like SDK telemetry does. That is the design rather than a shortcut.
The failure you are ruling out is silent. With perf_event_paranoid above 1, the agent starts, holds every capability it asked for, passes its own internal checks, logs nothing alarming — and collects nothing at all.Every check below exists because “the process is up” does not answer the question.

​
The four checks, in order

1

The process is running

If it is not, the reason is almost always a missing capability, and the startup message names exactly which. See Troubleshooting.
2

Probes actually attached

On Kubernetes:
A line reading opening perf event: permission denied confirms the silent failure. Fix it on the host or node:
3

The agent can see other processes

If it discovered only itself, it has no shared PID namespace: --pid=host under Docker, pid: host in Compose, hostPID: true on Kubernetes (the chart sets it).The symptom is a service inventory that did not grow.
4

aiAxonIQ accepted the data

Open Get Started in the dashboard. The ingest step lights up on the first accepted batch, and Services Discovered fills in.A rejected license key shows as 401 in the agent log — see Troubleshooting.

​
What you should see in the product

Nothing in aiAxonIQ was changed to accommodate the agent, so verification uses the ordinary surfaces. Within a minute or two of the agent attaching:
The agent’s telemetry is indistinguishable from SDK telemetry, because it is ordinary OTLP. Verification reads the same key-usage timestamp, the same overview counters and the same span-derived service names it always did — none of which know or care what produced the batch.That is the design, not a shortcut: it is why there is no separate “is the agent working” page in the product to keep in sync with reality.

​
Confirm the privilege you actually got

Intent and reality diverge quietly — a chart default that moved, an upgrade that regenerated a unit, a flag that was not accepted. The audit tool reports what the running agent actually holds:
Run it after every install and every upgrade. “We deployed profile B” is a belief until this has been run once.

​
When something is missing

The most common outcome is not “nothing” but “some services”. That is a different problem with different causes — TLS library coverage, discovery scope, or a protocol the agent does not decode. See Only some services appear.

​
Collecting diagnostics

If you need to hand something to support:
It collects configuration, versions, capability state, host facts and recent logs into an archive, with the license key and other credentials redacted. If redaction cannot be completed the bundle deletes itself rather than write a file that leaks.

​
Next

Troubleshooting

Symptom to cause to fix, in likelihood order.

Performance

What drives overhead and how to measure it on your own hosts.

Known limitations

What is missing on purpose.