diff --git a/ai-engineering/evaluate/setup.mdx b/ai-engineering/evaluate/setup.mdx index a75fb539..dd343242 100644 --- a/ai-engineering/evaluate/setup.mdx +++ b/ai-engineering/evaluate/setup.mdx @@ -5,7 +5,7 @@ keywords: ["ai engineering", "setup", "authentication", "cli", "install"] sidebarTitle: "Setup and auth" --- -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" This guide walks you through installing the Axiom AI SDK and authenticating with the Axiom AI SDK CLI so your evaluation results are tracked and attributed correctly in the Axiom Console. @@ -84,13 +84,13 @@ Instead of using OAuth, you can authenticate using environment variables: export AXIOM_TOKEN="API_TOKEN" export AXIOM_DATASET="DATASET_NAME" export AXIOM_ORG_ID="ORGANIZATION_ID" -export AXIOM_URL="AXIOM_EDGE_DOMAIN" +export AXIOM_URL="AXIOM_DOMAIN" ``` Replace `ORGANIZATION_ID` with the organization ID. - + ## Create the Axiom configuration file diff --git a/ai-engineering/quickstart.mdx b/ai-engineering/quickstart.mdx index 0a156502..d47f9ddd 100644 --- a/ai-engineering/quickstart.mdx +++ b/ai-engineering/quickstart.mdx @@ -5,7 +5,7 @@ keywords: ["ai engineering", "getting started", "install", "setup", "configurati --- import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" import AIInstrumentationApproaches from "/snippets/ai-instrumentation-approaches.mdx" @@ -200,7 +200,7 @@ export default defineConfig({ Store environment variables in an `.env` file in the root of your project: ```bash .env -AXIOM_URL="AXIOM_EDGE_DOMAIN" +AXIOM_URL="AXIOM_DOMAIN" AXIOM_TOKEN="API_TOKEN" AXIOM_DATASET="DATASET_NAME" OPENAI_API_KEY="" @@ -211,7 +211,7 @@ ANTHROPIC_API_KEY="" - + Enter the API keys for the LLMs you want to work with. diff --git a/apps/hex.mdx b/apps/hex.mdx index 6fcb1a9c..6c293bd5 100644 --- a/apps/hex.mdx +++ b/apps/hex.mdx @@ -6,7 +6,7 @@ sidebarTitle: 'Hex' import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDataset from "/snippets/replace-dataset.mdx" Hex is a powerful collaborative data platform that allows you to create notebooks with Python/SQL code and interactive visualizations. @@ -21,7 +21,7 @@ This page explains how to integrate Hex with Axiom to visualize geospatial data Send your sample location data to Axiom using the API endpoint. For example, the following HTTP request sends sample robot location data with latitude, longitude, status, and satellite information. ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/json' \ -d '[ @@ -39,7 +39,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ - + Verify that your data has been ingested correctly by running an APL query in the Axiom UI. diff --git a/guides/send-logs-from-apache-log4j.mdx b/guides/send-logs-from-apache-log4j.mdx index 7d237f1d..523662a5 100644 --- a/guides/send-logs-from-apache-log4j.mdx +++ b/guides/send-logs-from-apache-log4j.mdx @@ -10,7 +10,7 @@ enlargeLogo: true import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" Log4j is a Java logging framework developed by the Apache Software Foundation and widely used in the Java community. This page covers how to get started with Log4j, configure it to forward log messages to Fluentd, and send logs to Axiom. @@ -354,7 +354,7 @@ To configure Fluentd, create a configuration file. Create a new file named `flue @type http - endpoint https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME + endpoint https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME headers {"Authorization":"Bearer API_TOKEN"} json_array true @@ -371,7 +371,7 @@ To configure Fluentd, create a configuration file. Create a new file named `flue - + This configuration does the following: diff --git a/guides/send-logs-from-dotnet.mdx b/guides/send-logs-from-dotnet.mdx index 9786ec4b..e2bf9c48 100644 --- a/guides/send-logs-from-dotnet.mdx +++ b/guides/send-logs-from-dotnet.mdx @@ -9,7 +9,7 @@ logoId: 'dotnet' import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" - [Install the .NET SDK](https://dotnet.microsoft.com/download). @@ -51,7 +51,7 @@ public static class AxiomLogger // Specify the Axiom dataset name and construct the API endpoint URL var datasetName = "DATASET_NAME"; - var axiomEdgeDomain = "AXIOM_EDGE_DOMAIN"; + var axiomEdgeDomain = "AXIOM_DOMAIN"; var axiomUri = $"https://{axiomEdgeDomain}/v1/ingest/{datasetName}"; // Replace with your Axiom API token @@ -95,7 +95,7 @@ public static class AxiomLogger - + ### Configure the main program @@ -415,7 +415,7 @@ Set up NLog by creating an `NLog.config` file or configuring it programmatically flushTimeout="5000"> @@ -436,7 +436,7 @@ Set up NLog by creating an `NLog.config` file or configuring it programmatically - + ### Configure the main program diff --git a/guides/send-logs-from-laravel.mdx b/guides/send-logs-from-laravel.mdx index f4aad715..f216090e 100644 --- a/guides/send-logs-from-laravel.mdx +++ b/guides/send-logs-from-laravel.mdx @@ -9,7 +9,7 @@ logoId: 'laravel' import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" This guide explains integrating Axiom as a logging solution in a Laravel app. Using Axiom’s capabilities with a custom log channel, you can efficiently send your app’s logs to Axiom for storage, analysis, and monitoring. This integration uses Monolog, Laravel’s underlying logging library, to create a custom logging handler that forwards logs to Axiom. @@ -133,14 +133,14 @@ The `default` configuration specifies the primary channel Laravel uses for loggi LOG_CHANNEL=axiom AXIOM_API_TOKEN=API_TOKEN AXIOM_DATASET=DATASET_NAME -AXIOM_DOMAIN=AXIOM_EDGE_DOMAIN +AXIOM_DOMAIN=AXIOM_DOMAIN LOG_LEVEL=debug LOG_DEPRECATIONS_CHANNEL=null ``` - + ### Deprecations log channel diff --git a/guides/send-logs-from-ruby-on-rails.mdx b/guides/send-logs-from-ruby-on-rails.mdx index 92c4dcbf..46c5e945 100644 --- a/guides/send-logs-from-ruby-on-rails.mdx +++ b/guides/send-logs-from-ruby-on-rails.mdx @@ -8,7 +8,7 @@ logoId: 'ruby' --- import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" This guide provides step-by-step instructions on how to send logs from a Ruby on Rails app to Axiom using the Faraday library. By following this guide, you configure your Rails app to send logs to Axiom, allowing you to monitor and analyze your app logs effectively. @@ -48,7 +48,7 @@ require 'json' class AxiomLogger def self.send_log(log_data) dataset_name = "DATASET_NAME" - axiom_ingest_api_url = "https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME" + axiom_ingest_api_url = "https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME" ingest_token = "API_TOKEN" conn = Faraday.new(url: axiom_ingest_api_url) do |faraday| @@ -75,7 +75,7 @@ end - + ## Test with the Axiom logger diff --git a/reference/limits.mdx b/reference/limits.mdx index 10663330..b4e7c693 100644 --- a/reference/limits.mdx +++ b/reference/limits.mdx @@ -25,7 +25,7 @@ The table below summarizes the limits applied to each pricing plan. For more det | Users | 1 | 1,000 * | | [Monitors](/monitor-data/monitors) | 3 | 500 * | | [Notifiers](/monitor-data/notifiers-overview) | Email, Discord | All supported | -| [Supported deployment regions](/reference/regions) | US | US | +| [Supported edge deployments](/reference/edge-deployments) | US | US | \* Soft limit that can be increased upon request. diff --git a/reference/organization-settings.mdx b/reference/organization-settings.mdx index 85c1f3a1..9f034f55 100644 --- a/reference/organization-settings.mdx +++ b/reference/organization-settings.mdx @@ -7,15 +7,15 @@ keywords: ['axiom documentation', 'documentation', 'axiom', 'api token', 'person import AiSetting from "/snippets/ai-setting.mdx" -## View organization ID +## Determine organization ID 1. Click **Settings > General**. 1. Find organization ID in the **ID** section. -## View organization region +## Determine organization edge deployment 1. Click **Settings > General**. -1. Find organization region in the **Region** section. +1. Find your organization’s default edge deployment in the **Edge deployment** section. For more information, see [Edge deployments](/reference/edge-deployments). diff --git a/reference/usage-billing.mdx b/reference/usage-billing.mdx index ff431d44..657f9aa3 100644 --- a/reference/usage-billing.mdx +++ b/reference/usage-billing.mdx @@ -87,7 +87,7 @@ To upgrade or downgrade your plan: You can manage the following add-ons: -- Additional regions +- Additional edge deployments - Audit log - Directory Sync - Role-Based Access Control (RBAC) diff --git a/restapi/ingest.mdx b/restapi/ingest.mdx index 9fd6d405..74caca51 100644 --- a/restapi/ingest.mdx +++ b/restapi/ingest.mdx @@ -7,7 +7,7 @@ keywords: ['axiom documentation', 'documentation', 'axiom', 'axiom api', 'rest a import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" The Axiom REST API accepts the following data formats: @@ -35,10 +35,10 @@ To send data to Axiom in JSON format: 1. Optional: In the body of the request, set optional parameters such as `timestamp-field` and `timestamp-format`. For more information, see the [ingest data API reference](/restapi/endpoints/ingestToDataset). 1. Set the `Content-Type` header to `application/json`. 1. Set the `Authorization` header to `Bearer API_TOKEN`. -1. Send the POST request to `https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME`. +1. Send the POST request to `https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME`. - + @@ -49,7 +49,7 @@ The following example request contains grouped events. The structure of the JSON **Example request** ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/json' \ -d '[ @@ -65,7 +65,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -87,7 +87,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ **Example request** ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/json' \ -d '[ @@ -133,7 +133,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -155,7 +155,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ **Example request** ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/json' \ -d '[{ "axiom": { @@ -177,7 +177,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -202,17 +202,17 @@ To send data to Axiom in NDJSON format: 1. Optional: In the body of the request, set optional parameters such as `timestamp-field` and `timestamp-format`. For more information, see the [ingest data API reference](/restapi/endpoints/ingestToDataset). 1. Set the `Content-Type` header to either `application/json` or `application/x-ndjson`. 1. Set the `Authorization` header to `Bearer API_TOKEN`. Replace `API_TOKEN` with the Axiom API token you have generated. -1. Send the POST request to `https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME`. Replace `DATASET_NAME` with the name of the Axiom dataset where you want to send data. +1. Send the POST request to `https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME`. Replace `DATASET_NAME` with the name of the Axiom dataset where you want to send data. - + **Example request** ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/x-ndjson' \ -d '{"id":1,"name":"machala"} @@ -224,7 +224,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -249,17 +249,17 @@ To send data to Axiom in JSON format: 1. Optional: In the body of the request, set optional parameters such as `timestamp-field` and `timestamp-format`. For more information, see the [ingest data API reference](/restapi/endpoints/ingestToDataset). 1. Set the `Content-Type` header to `text/csv`. 1. Set the `Authorization` header to `Bearer API_TOKEN`. Replace `API_TOKEN` with the Axiom API token you have generated. -1. Send the POST request to `https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME`. Replace `DATASET_NAME` with the name of the Axiom dataset where you want to send data. +1. Send the POST request to `https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME`. Replace `DATASET_NAME` with the name of the Axiom dataset where you want to send data. - + **Example request** ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: text/csv' \ -d 'user, name @@ -267,7 +267,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -296,7 +296,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + diff --git a/restapi/introduction.mdx b/restapi/introduction.mdx index 4b8ae4ab..40be2ec9 100644 --- a/restapi/introduction.mdx +++ b/restapi/introduction.mdx @@ -11,7 +11,7 @@ popularityOrder: 1 --- import Prerequisites from "/snippets/minimal-prerequisites.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" import BaseDomains from "/snippets/base-domains.mdx" @@ -26,7 +26,7 @@ Axiom API follows the REST architectural style and uses JSON for serialization. For example, the following curl command ingests data to an Axiom dataset: ```bash -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/json' \ -d '[ @@ -37,7 +37,7 @@ curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ ``` - + @@ -47,11 +47,11 @@ For more information, see [Send data to Axiom via API](/restapi/ingest) and [Ing The base domain of an API request depends on the following: -- To ingest data, use the [Ingest data endpoint](/restapi/endpoints/ingestToDataset) with the base domain of your region. +- To ingest data, use the [Ingest data endpoint](/restapi/endpoints/ingestToDataset) with the base domain of your edge deployment. - For more information on regions, see [Edge deployments](/reference/edge-deployments). + For more information on edge deployments, see [Edge deployments](/reference/edge-deployments). - For all other API endpoints, use the base domain `https://api.axiom.co`. diff --git a/send-data/aws-firehose.mdx b/send-data/aws-firehose.mdx index 2acf6a1c..82ee80b7 100644 --- a/send-data/aws-firehose.mdx +++ b/send-data/aws-firehose.mdx @@ -10,7 +10,7 @@ logoId: 'firehose' import AwsDisclaimer from "/snippets/aws-disclaimer.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDataset from "/snippets/replace-dataset.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" Amazon Data Firehose is a service for delivering real-time streaming data to different destinations. Send event data from Amazon Data Firehose to Axiom to analyse and monitor your data efficiently. @@ -23,9 +23,9 @@ Amazon Data Firehose is a service for delivering real-time streaming data to dif 1. In Axiom, determine the ID of the dataset you’ve created. 1. In Amazon Data Firehose, create an HTTP endpoint destination. For more information, see the [Amazon Data Firehose documentation](https://docs.aws.amazon.com/firehose/latest/dev/create-destination.html#create-destination-http). -1. Set HTTP endpoint URL to `https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME/firehose`. +1. Set HTTP endpoint URL to `https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME/firehose`. - + 1. Set the access key to the Axiom API token. diff --git a/send-data/aws-firelens.mdx b/send-data/aws-firelens.mdx index 151b3259..d98f618b 100644 --- a/send-data/aws-firelens.mdx +++ b/send-data/aws-firelens.mdx @@ -8,7 +8,7 @@ logoId: 'awsEC2' --- import Prerequisites from "/snippets/standard-prerequisites.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" import AwsDisclaimer from "/snippets/aws-disclaimer.mdx" @@ -40,7 +40,7 @@ You’ll typically define this in a file called `fluent-bit.conf`: [OUTPUT] Name http Match * - Host AXIOM_EDGE_DOMAIN + Host AXIOM_DOMAIN Port 443 URI /v1/ingest/DATASET_NAME Format json_lines @@ -52,7 +52,7 @@ You’ll typically define this in a file called `fluent-bit.conf`: ``` - + @@ -104,14 +104,14 @@ Create the `fluentd.conf` file and add your configuration: @type http headers {"Authorization": "Bearer API_TOKEN"} data_type json - endpoint https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME + endpoint https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME sourcetype ecs ``` - + Read more about [Fluentd configuration here](/send-data/fluentd) diff --git a/send-data/aws-iot-rules.mdx b/send-data/aws-iot-rules.mdx index 14222113..e322ca26 100644 --- a/send-data/aws-iot-rules.mdx +++ b/send-data/aws-iot-rules.mdx @@ -9,7 +9,7 @@ logoId: 'awsIotCore' import AwsDisclaimer from "/snippets/aws-disclaimer.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" @@ -29,10 +29,10 @@ import requests # Import the requests module to make HTTP requests def lambda_handler(event, context): # Retrieve the dataset name and the Axiom domain from the environment variables dataset_name = os.environ['DATASET_NAME'] - axiom_edge_domain = os.environ['AXIOM_EDGE_DOMAIN'] + axiom_domain = os.environ['AXIOM_DOMAIN'] # Construct the Axiom API URL using the dataset name - axiom_api_url = f"https://{axiom_edge_domain}/v1/ingest/{dataset_name}" + axiom_api_url = f"https://{axiom_domain}/v1/ingest/{dataset_name}" # Retrieve the Axiom API token from the environment variable api_token = os.environ['API_TOKEN'] @@ -62,7 +62,7 @@ def lambda_handler(event, context): In the environment variables section of the Lambda function configuration, add the following environment variables: - + This example uses Python for the Lambda function. To use another language, change the code above accordingly. diff --git a/send-data/aws-s3.mdx b/send-data/aws-s3.mdx index 12c27553..3a06eca5 100644 --- a/send-data/aws-s3.mdx +++ b/send-data/aws-s3.mdx @@ -9,7 +9,7 @@ logoId: 'awsbucket' import AwsDisclaimer from "/snippets/aws-disclaimer.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" This page explains how to set up an AWS Lambda function to send logs from an S3 bucket to Axiom. The Lambda function triggers when a new log file is uploaded to an S3 bucket, processes the log data, and sends it to Axiom. @@ -104,7 +104,7 @@ def lambda_handler(event, context): # Prepare Axiom API request dataset_name = os.environ['DATASET_NAME'] - axiom_edge_domain = os.environ['AXIOM_EDGE_DOMAIN'] + axiom_edge_domain = os.environ['AXIOM_DOMAIN'] axiom_api_url = f"https://{axiom_edge_domain}/v1/ingest/{dataset_name}" api_token = os.environ['API_TOKEN'] axiom_headers = { @@ -127,7 +127,7 @@ def lambda_handler(event, context): In the environment variables section of the Lambda function configuration, add the following environment variables: - + This example uses Python for the Lambda function. To use another language, change the code above accordingly. diff --git a/send-data/cribl.mdx b/send-data/cribl.mdx index 5a410849..d1aa465a 100644 --- a/send-data/cribl.mdx +++ b/send-data/cribl.mdx @@ -9,7 +9,7 @@ isPopular: true popularityOrder: 10 --- -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDataset from "/snippets/replace-dataset.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceToken from "/snippets/replace-token.mdx" @@ -36,10 +36,10 @@ Open Cribl’s UI and navigate to **Destinations > HTTP**. Click on `+` Add New - **Name:** Choose a name for the destination. -- **Endpoint URL:** The URL of your Axiom log ingest endpoint `https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME`. +- **Endpoint URL:** The URL of your Axiom log ingest endpoint `https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME`. - + diff --git a/send-data/fluent-bit.mdx b/send-data/fluent-bit.mdx index 7ce18585..5bef3e19 100644 --- a/send-data/fluent-bit.mdx +++ b/send-data/fluent-bit.mdx @@ -10,7 +10,7 @@ popularityOrder: 11 --- import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" Fluent Bit is an open-source log processor and forwarder that allows you to collect any data like metrics and logs from different sources, enrich them with filters, and send them to multiple destinations like Axiom. @@ -27,7 +27,7 @@ Fluent Bit is an open-source log processor and forwarder that allows you to coll [OUTPUT] Name http Match * - Host AXIOM_EDGE_DOMAIN + Host AXIOM_DOMAIN Port 443 URI /v1/ingest/DATASET_NAME Header Authorization Bearer API_TOKEN @@ -39,6 +39,6 @@ Fluent Bit is an open-source log processor and forwarder that allows you to coll ``` - + diff --git a/send-data/fluentd.mdx b/send-data/fluentd.mdx index bbb37789..0f3ccee0 100644 --- a/send-data/fluentd.mdx +++ b/send-data/fluentd.mdx @@ -12,7 +12,7 @@ popularityOrder: 12 import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" import ReplaceDataset from "/snippets/replace-dataset.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" Fluentd is an open-source log collector that allows you to collect, aggregate, process, analyze, and route log files. @@ -49,7 +49,7 @@ The example below shows a Fluentd configuration that sends data to Axiom using t @type http - endpoint https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME + endpoint https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME # Authorization Bearer should be an ingest token headers {"Authorization": "Bearer API_TOKEN"} json_array false @@ -66,7 +66,7 @@ The example below shows a Fluentd configuration that sends data to Axiom using t ``` - + @@ -257,7 +257,7 @@ The example below shows a Fluentd configuration that sends Scala data to Axiom # Send Scala logs using HTTP plugin to Axiom @type http - endpoint "#{ENV['FLUENT_HTTP_ENDPOINT'] || 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME'}" + endpoint "#{ENV['FLUENT_HTTP_ENDPOINT'] || 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME'}" headers {"Authorization": "Bearer #{ENV['FLUENT_HTTP_TOKEN'] || ''}"} @type json @@ -275,7 +275,7 @@ The example below shows a Fluentd configuration that sends Scala data to Axiom ``` - + diff --git a/send-data/heroku-log-drains.mdx b/send-data/heroku-log-drains.mdx index 23a2413b..24ba82ce 100644 --- a/send-data/heroku-log-drains.mdx +++ b/send-data/heroku-log-drains.mdx @@ -9,7 +9,7 @@ logoId: 'heroku' import Prerequisites from "/snippets/standard-prerequisites.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" Log Drains make it easy to collect logs from your deployments and forward them to archival, search, and alerting services by sending them via HTTPS, HTTP, TLS, and TCP. @@ -28,12 +28,12 @@ Sign up and login to your account on [Heroku](https://heroku.com/), and download Heroku log drains configuration consists of three main components ```bash -heroku drains:add https://axiom:API_TOKEN@AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME -a HEROKU_APPLICATION_NAME +heroku drains:add https://axiom:API_TOKEN@AXIOM_DOMAIN/v1/ingest/DATASET_NAME -a HEROKU_APPLICATION_NAME ``` - + Replace `HEROKU_APPLICATION_NAME` with the name of the app that you created on the Heroku dashboard or the Heroku CLI. diff --git a/send-data/kubernetes.mdx b/send-data/kubernetes.mdx index 40c24a76..bd2ef7f0 100644 --- a/send-data/kubernetes.mdx +++ b/send-data/kubernetes.mdx @@ -8,7 +8,7 @@ logoId: 'kubernetes' --- import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import Prerequisites from "/snippets/standard-prerequisites.mdx" Axiom makes it easy to collect, analyze, and monitor logs from your Kubernetes clusters. Integrate popular tools like Filebeat, Vector, or Fluent Bit with Axiom to send your cluster logs. @@ -113,7 +113,7 @@ spec: - -e env: - name: AXIOM_HOST - value: AXIOM_EDGE_DOMAIN + value: AXIOM_DOMAIN - name: AXIOM_DATASET_NAME value: DATASET_NAME - name: AXIOM_API_TOKEN @@ -276,7 +276,7 @@ spec: - /etc/vector/ env: - name: AXIOM_HOST - value: AXIOM_EDGE_DOMAIN + value: AXIOM_DOMAIN - name: AXIOM_DATASET_NAME value: DATASET_NAME - name: AXIOM_API_TOKEN @@ -464,7 +464,7 @@ spec: image: fluent/fluent-bit:1.9.9 env: - name: AXIOM_HOST - value: AXIOM_EDGE_DOMAIN + value: AXIOM_DOMAIN - name: AXIOM_DATASET_NAME value: DATASET_NAME - name: AXIOM_API_TOKEN @@ -495,7 +495,7 @@ spec: ``` - + diff --git a/send-data/methods.mdx b/send-data/methods.mdx index e9929c21..46ba0e30 100644 --- a/send-data/methods.mdx +++ b/send-data/methods.mdx @@ -5,20 +5,20 @@ sidebarTitle: "Methods" keywords: ["send data", "ingest", "methods", "integrations", "opentelemetry", "vector", "fluentd"] --- -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" The easiest way to send your first event data to Axiom is with a direct HTTP request using a tool like `cURL`. ```shell -curl -X 'POST' 'https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME' \ +curl -X 'POST' 'https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME' \ -H 'Authorization: Bearer API_TOKEN' \ -H 'Content-Type: application/x-ndjson' \ -d '{ "http": { "request": { "method": "GET", "duration_ms": 231 }, "response": { "body": { "size": 3012 } } }, "url": { "path": "/download" } }' ``` - + diff --git a/send-data/syslog-proxy.mdx b/send-data/syslog-proxy.mdx index b5b14b22..8174e4f6 100644 --- a/send-data/syslog-proxy.mdx +++ b/send-data/syslog-proxy.mdx @@ -88,7 +88,7 @@ Set the following environment variables to connect to Axiom: - `AXIOM_TOKEN` is the Axiom API token you have generated. - `AXIOM_DATASET` is the name of the Axiom dataset where you want to send data. -- Optional: `AXIOM_URL` is the URL of the Axiom API. By default, it uses the US region. Change the default value if your organization uses another region. For more information, see [Edge deployments](/reference/edge-deployments). +- Optional: `AXIOM_URL` is the URL of the Axiom API. By default, it uses the `US East 1 (AWS)` edge deployment. Change the default value if your organization uses another edge deployment. For more information, see [Edge deployments](/reference/edge-deployments). ## Run Axiom Syslog Proxy diff --git a/send-data/tremor.mdx b/send-data/tremor.mdx index 83a83552..73fdc0f3 100644 --- a/send-data/tremor.mdx +++ b/send-data/tremor.mdx @@ -8,7 +8,7 @@ logoId: 'tremor' --- import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx" -import ReplaceEdgeDomain from "/snippets/replace-edge-domain.mdx" +import ReplaceDomain from "/snippets/replace-domain.mdx" Axiom provides a unique way of ingesting [Tremor logs](https://www.tremor.rs/) into Axiom. With your connector definitions, you can configure Tremor connectors and events components to interact with your external systems, such as databases, message queues, or APIs, and eventually ingest data from these sources into Axiom. @@ -45,7 +45,7 @@ flow token with config = { - "url": "https://AXIOM_EDGE_DOMAIN/v1/ingest/#{args.dataset}", + "url": "https://AXIOM_DOMAIN/v1/ingest/#{args.dataset}", "tls": true, "method": "POST", "headers": { @@ -77,7 +77,7 @@ This assumes you have set `TREMOR_PATH` in your environment pointing to `tremor- - + ## Configuration using Syslog diff --git a/snippets/replace-domain.mdx b/snippets/replace-domain.mdx index 3c6b19cb..5abcf2a9 100644 --- a/snippets/replace-domain.mdx +++ b/snippets/replace-domain.mdx @@ -1 +1 @@ -Replace `AXIOM_DOMAIN` with `api.axiom.co` if your organization uses the US region. For more information, see [Edge deployments](/reference/edge-deployments). +Replace `AXIOM_DOMAIN` with the base domain of your edge deployment. For more information, see [Edge deployments](/reference/edge-deployments). diff --git a/snippets/replace-edge-domain.mdx b/snippets/replace-edge-domain.mdx deleted file mode 100644 index ca13202d..00000000 --- a/snippets/replace-edge-domain.mdx +++ /dev/null @@ -1 +0,0 @@ -Replace `AXIOM_EDGE_DOMAIN` with `https://us-east-1.aws.edge.axiom.co` if your organization uses the US region, and with `https://eu-central-1.aws.edge.axiom.co` if your organization uses the EU region. For more information, see [Edge deployments](/reference/edge-deployments).