Send data from Python app to Axiom
This page explains how to send data from a Python app to Axiom.
To send data from a Python app to Axiom, use the Axiom Python SDK.
Prerequisites
- Create an Axiom account.
- Create a dataset in Axiom where you send your data.
- Create an API token in Axiom with permissions to ingest data to the dataset you have created.
Install SDK
If you use the Axiom CLI, run eval $(axiom config export -f) to configure your environment variables. Otherwise, create an API token and export it as AXIOM_TOKEN.
You can also configure the client using options passed to the client constructor:
Use client
For more examples, see the examples in GitHub.
Configure region
By default, the client sends data to api.axiom.co. To target a specific edge region, pass the edge argument with the edge domain that matches the region your dataset lives in:
The following edge domains are available:
| Edge deployment | Base domain for ingest and query |
|---|---|
| US East 1 (AWS) | us-east-1.aws.edge.axiom.co |
| EU Central 1 (AWS) | eu-central-1.aws.edge.axiom.co |
For more information about edge deployments, see Edge deployments.
To point at a custom edge endpoint such as a proxy or load balancer, use edge_url="https://your-edge-host" instead. edge_url takes precedence over edge if both are set.
Example with AxiomHandler
The example below uses AxiomHandler to send logs from the logging module to Axiom:
For a full example, see GitHub.
Example with structlog
The example below uses structlog to send logs to Axiom. structlog isn't a dependency of the Axiom Python SDK, so install it separately with pip install structlog.
AxiomProcessor passes the event dictionary on unchanged so that later processors can run. Place a renderer such as structlog.dev.ConsoleRenderer() after it as the last processor. Without a renderer, structlog's logger receives a dictionary and raises a TypeError.
For a full example, see GitHub.