Use only AXIOM_DOMAIN placeholder for edges (#487)

Author: manototh

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"
 ```
 
 <Info>
 <ReplaceDatasetToken />
 Replace `ORGANIZATION_ID` with the organization ID.
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 ## Create the Axiom configuration file

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=""
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 
 Enter the API keys for the LLMs you want to work with.
 </Info>

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' \
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 Verify that your data has been ingested correctly by running an APL query in the Axiom UI.

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
 
 <match **>
   @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
   <buffer>
@@ -371,7 +371,7 @@ To configure Fluentd, create a configuration file. Create a new file named `flue
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 This configuration does the following:

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"
 
 <Prerequisites />
 - [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
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 ### Configure the main program
@@ -415,7 +415,7 @@ Set up NLog by creating an `NLog.config` file or configuring it programmatically
                 flushTimeout="5000">
             <target xsi:type="HTTP" 
                     name="axiom"
-                    url="https://AXIOM_EDGE_DOMAIN/v1/ingest/DATASET_NAME"
+                    url="https://AXIOM_DOMAIN/v1/ingest/DATASET_NAME"
                     HttpHeaders="Authorization: Bearer API_TOKEN"
                     contentType="application/json">
                 <layout xsi:type="JsonLayout" includeAllProperties="true">
@@ -436,7 +436,7 @@ Set up NLog by creating an `NLog.config` file or configuring it programmatically
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 ### Configure the main program

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
 ```
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 ### Deprecations log channel

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
 
 <Info>
 <ReplaceDatasetToken />
-<ReplaceEdgeDomain />
+<ReplaceDomain />
 </Info>
 
 ## Test with the Axiom logger

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.
 

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 <Icon icon="gear" iconType="solid"/> **Settings > General**.
 1. Find organization ID in the **ID** section.
 
-## View organization region
+## Determine organization edge deployment
 
 1. Click <Icon icon="gear" iconType="solid"/> **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).
 

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)