Start here
How it works
The path your data takes, and the two properties of it that explain most of
what you will run into later.
Create a license key
The credential every ingest request carries. What it does, and the four
things it deliberately does not control.
Send data with OpenTelemetry
Endpoints, the authentication header, and a first request you can verify
with curl before touching your application.
Verify your data arrived
Telling “accepted” apart from “queryable” — the distinction behind most
first-install confusion.
Send data from where you run
Kubernetes
A DaemonSet collector for node telemetry, and the second collector most
clusters end up needing.
Any application
Zero-code instrumentation for Node.js, Python, Java and .NET; an explicit
setup for Go.
Prometheus
Remote-write from an existing Prometheus server. A config change on one
side and nothing on your services.
Then use it
Search logs
Field filters, booleans, wildcards and numeric comparisons, with the full
field list.
Alerting
Rule types that actually evaluate, the three comparators, and which
channels work out of the box.
Synthetic monitoring
HTTP, SSL, DNS, TCP and multi-step checks run against your endpoints from
outside.
The three things you need
1
A license key
Created in Settings → License Keys, sent as the
X-License-Key header.
See Create a license key.2
An endpoint
The receiver’s OTLP address, which differs per deployment. Get Started
in the dashboard shows the one that is correct for yours.
3
An exporter
Any OpenTelemetry SDK, or the OpenTelemetry Collector. aiAxonIQ speaks
standard OTLP, so there is nothing vendor-specific to install and nothing
to rewrite if you later point the same exporter elsewhere.
Not sure where a problem is?
Troubleshooting splits the pipeline into four
stages and tells you which one you are in — usually in about a minute, which
eliminates most of the list before you start reading.