> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiaxoniq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# aiAxonIQ documentation

> Send OpenTelemetry logs, metrics and traces to aiAxonIQ, then search, alert and investigate. Start here to get your first data flowing in about ten minutes.

aiAxonIQ ingests OpenTelemetry logs, metrics and traces, plus Prometheus
remote-write. You point an exporter at an endpoint, authenticate with a license
key, and the data becomes queryable.

There is no aiAxonIQ agent and no aiAxonIQ SDK. The thing you install is the
upstream OpenTelemetry tooling for your language or platform, with two settings
changed — which also means nothing here locks you in.

## Start here

<CardGroup cols={2}>
  <Card title="How it works" icon="diagram-project" href="/get-started/how-it-works">
    The path your data takes, and the two properties of it that explain most of
    what you will run into later.
  </Card>

  <Card title="Create a license key" icon="key" href="/get-started/license-keys">
    The credential every ingest request carries. What it does, and the four
    things it deliberately does not control.
  </Card>

  <Card title="Send data with OpenTelemetry" icon="telescope" href="/send-data/otel/collector">
    Endpoints, the authentication header, and a first request you can verify
    with curl before touching your application.
  </Card>

  <Card title="Verify your data arrived" icon="circle-check" href="/get-started/verify-data">
    Telling "accepted" apart from "queryable" — the distinction behind most
    first-install confusion.
  </Card>
</CardGroup>

## Send data from where you run

<CardGroup cols={3}>
  <Card title="Kubernetes" icon="dharmachakra" href="/send-data/platforms/kubernetes">
    A DaemonSet collector for node telemetry, and the second collector most
    clusters end up needing.
  </Card>

  <Card title="Any application" icon="code" href="/send-data/otel/zero-code">
    Zero-code instrumentation for Node.js, Python, Java and .NET; an explicit
    setup for Go.
  </Card>

  <Card title="Prometheus" icon="chart-line" href="/send-data/prometheus">
    Remote-write from an existing Prometheus server. A config change on one
    side and nothing on your services.
  </Card>
</CardGroup>

## Then use it

<CardGroup cols={3}>
  <Card title="Search logs" icon="magnifying-glass" href="/guides/logs/search">
    Field filters, booleans, wildcards and numeric comparisons, with the full
    field list.
  </Card>

  <Card title="Alerting" icon="bell" href="/guides/alerts/overview">
    Rule types that actually evaluate, the three comparators, and which
    channels work out of the box.
  </Card>

  <Card title="Synthetic monitoring" icon="heart-pulse" href="/guides/synthetics/overview">
    HTTP, SSL, DNS, TCP and multi-step checks run against your endpoints from
    outside.
  </Card>
</CardGroup>

## The three things you need

<Steps>
  <Step title="A license key">
    Created in **Settings → License Keys**, sent as the `X-License-Key` header.
    See [Create a license key](/get-started/license-keys).
  </Step>

  <Step title="An endpoint">
    The receiver's OTLP address, which differs per deployment. **Get Started**
    in the dashboard shows the one that is correct for yours.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Note>
  **Not sure where a problem is?**
  [Troubleshooting](/support/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.
</Note>