axiomhq · tothmano · Jul 2, 2025
diff --git a/apps/hex.mdx b/apps/hex.mdx
@@ -14,7 +14,6 @@
 This page explains how to integrate Hex with Axiom to visualize geospatial data from your logs. You ingest location data into Axiom, query it using APL, and create interactive map visualizations in Hex.
 
 <Prerequisites />
-{/* list separator */}
 - [Create a Hex account](https://app.hex.tech/).
 
 ## Send geospatial data to Axiom
@@ -107,7 +106,7 @@
                columns = [field['name'] for field in table['fields']]
                rows = table['columns']

                # Create DataFrame with proper column orientation
                df = pd.DataFrame(list(zip(*rows)), columns=columns)

                # Ensure data types are appropriate for mapping

diff --git a/apps/tailscale.mdx b/apps/tailscale.mdx
@@ -14,12 +14,11 @@
 Integrating Axiom with Tailscale allows you to stream your audit and network flow logs directly to Axiom seamlessly, unlocking powerful insights and analysis. Whether you’re conducting a security audit, optimizing performance, or ensuring compliance, Axiom’s Tailscale dashboard equips you with the tools to maintain a secure and efficient network, respond quickly to potential issues, and make informed decisions about your network configuration and usage.
 
 <Prerequisites />
-{/* list separator */}
 - [Create a Tailscale account](https://login.tailscale.com/start).
 
 ## Setup

 1. In Tailscale, go to the [configuration logs page](https://login.tailscale.com/admin/logs) of the admin console.
 2. Add Axiom as a configuration log streaming destination in Tailscale. For more information, see the [Tailscale documentation](https://tailscale.com/kb/1255/log-streaming?q=stream#add-a-configuration-log-streaming-destination).

 ## Tailscale dashboard

diff --git a/dashboard-elements/monitor-list.mdx b/dashboard-elements/monitor-list.mdx
@@ -9,7 +9,6 @@
 The monitor list dashboard element provides a visual overview of the monitors you specify. It offers a quick glance into important developments about the monitors such as their status and history.
 
 <Prerequisites />
-{/* list separator */}
 - [Create a monitor](/monitor-data/monitors).
 
 ## Create monitor list
@@ -18,7 +17,7 @@
 1. Click <img src="/doc-assets/icons/plus.svg" className="inline-icon" alt="Add element" /> **Add element** in the top right corner.
 1. Click **Monitor list** from the list.
 1. In **Columns**, select the type of information you want to display for each monitor:
    - **Status** displays if the monitor state is normal, triggered, or disabled.
    - **History** provides a visual overview of the recent runs of the monitor. Green squares mean normal operation and red squares mean triggered state.
    - **Dataset** is the name of the dataset on which the monitor operates.
    - **Type** is the type of the monitor.

diff --git a/guides/opentelemetry-cloudflare-workers.mdx b/guides/opentelemetry-cloudflare-workers.mdx
@@ -14,7 +14,6 @@ import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx"
 This guide demonstrates how to configure OpenTelemetry in Cloudflare Workers to send telemetry data to Axiom using the [OTel CF Worker package](https://github.com/evanderkoogh/otel-cf-workers).
 
 <Prerequisites />
-{/* list separator */}
 - Create a Cloudflare account.
 - [Install Wrangler](https://developers.cloudflare.com/workers/wrangler/install-and-update/), the CLI tool for Cloudflare.
 

diff --git a/guides/opentelemetry-django.mdx b/guides/opentelemetry-django.mdx
@@ -12,7 +12,6 @@ import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx"
 import ReplaceDomain from "/snippets/replace-domain.mdx"
 
 <Prerequisites />
-{/* list separator */}
 - [Install Python version 3.7 or higher](https://www.python.org/downloads/).
 
 ## Install required dependencies

diff --git a/guides/opentelemetry-dotnet.mdx b/guides/opentelemetry-dotnet.mdx
@@ -11,12 +11,11 @@
 import ReplaceDomain from "/snippets/replace-domain.mdx"
 import Prerequisites from "/snippets/standard-prerequisites.mdx"

 OpenTelemetry provides a [unified approach to collecting telemetry data](https://opentelemetry.io/docs/languages/net/) from your .NET applications. This guide explains how to configure OpenTelemetry in a .NET application to send telemetry data to Axiom using the OpenTelemetry SDK.
 
 <Prerequisites />
-{/* list separator */}
 - Install the .NET 6.0 SDK on your development machine.
 - Use your existing .NET application or start with the sample provided in the `program.cs` below.
 
 ## Install dependencies


diff --git a/guides/opentelemetry-java.mdx b/guides/opentelemetry-java.mdx
@@ -14,7 +14,6 @@ import ReplaceDomain from "/snippets/replace-domain.mdx"
 OpenTelemetry provides a unified approach to collecting telemetry data from your Java applications. This page demonstrates how to configure OpenTelemetry in a Java app to send telemetry data to Axiom using the OpenTelemetry SDK.
 
 <Prerequisites />
-{/* list separator */}
 - [Install JDK 11](https://www.oracle.com/java/technologies/java-se-glance.html) or later
 - [Install Maven](https://maven.apache.org/download.cgi)
 - Use your own app written in Java or the provided `DiceRollerApp.java` sample.

diff --git a/guides/opentelemetry-python.mdx b/guides/opentelemetry-python.mdx
@@ -16,7 +16,6 @@ This guide explains how to send OpenTelemetry data from a Python app to Axiom us
 ## Prerequisites
 
 <Prerequisites />
-{/* list separator */}
 - Install Python version 3.7 or higher.
 
 ## Install required dependencies

diff --git a/guides/opentelemetry-ruby.mdx b/guides/opentelemetry-ruby.mdx
@@ -11,14 +11,13 @@
 import ReplaceDomain from "/snippets/replace-domain.mdx"
 import Prerequisites from "/snippets/standard-prerequisites.mdx"

 This guide provides detailed steps on how to configure OpenTelemetry in a Ruby application to send telemetry data to Axiom using the [OpenTelemetry Ruby SDK](https://opentelemetry.io/docs/languages/ruby/).
 
 <Prerequisites />
-{/* list separator */}
 - Install a [Ruby version manager](https://www.ruby-lang.org/en/documentation/installation/) like `rbenv` and use it to install the latest Ruby version.
 - Install [Rails](https://guides.rubyonrails.org/v5.0/getting_started.html) using the `gem install rails` command.
 
 ## Set up the Ruby on Rails application

 1. Create a new Rails app using the `rails new myapp` command.
 2. Go to the app directory with the `cd myapp` command.

diff --git a/guides/send-logs-from-apache-log4j.mdx b/guides/send-logs-from-apache-log4j.mdx
@@ -15,7 +15,6 @@ 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.
 
 <Prerequisites />
-{/* list separator */}
 - [Install JDK 11](https://www.oracle.com/java/technologies/java-se-glance.html) or later
 - [Install Maven](https://maven.apache.org/download.cgi)
 - [Install Fluentd](https://www.fluentd.org/download)

diff --git a/guides/send-logs-from-dotnet.mdx b/guides/send-logs-from-dotnet.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Send logs from a .NET app'
 description: 'This guide explains how to set up and configure logging in a .NET application, and how to send logs to Axiom.'
 overview: 'Free, open-source development platform for building various applications'
 sidebarTitle: .NET
 keywords: ['guides', 'dotnet', 'C#', '.net']
@@ -12,7 +12,6 @@
 import ReplaceDomain from "/snippets/replace-domain.mdx"
 
 <Prerequisites />
-{/* list separator */}
 - [Install the .NET SDK](https://dotnet.microsoft.com/download).
 
 ## Option 1: Using HTTP Client

diff --git a/guides/send-logs-from-laravel.mdx b/guides/send-logs-from-laravel.mdx
@@ -1,7 +1,7 @@
 ---
 title: 'Send logs from Laravel to Axiom'
 description: 'This guide demonstrates how to configure logging in a Laravel app to send logs to Axiom'
 overview: 'PHP web application framework with expressive, elegant syntax'
 sidebarTitle: Laravel
 keywords: ['guides', 'laravel', 'php']
 logoId: 'laravel'
@@ -14,7 +14,6 @@
 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.
 
 <Prerequisites />
-{/* list separator */}
 - PHP development [environment](https://www.php.net/manual/en/install.php)
 - [Composer](https://laravel.com/docs/11.x/installation) installed on your system
 - Laravel app setup

diff --git a/guides/send-logs-from-ruby-on-rails.mdx b/guides/send-logs-from-ruby-on-rails.mdx
@@ -1,7 +1,7 @@
 ---
 title: 'Send logs from a Ruby on Rails application using Faraday'
 description: 'This guide provides step-by-step instructions on how to send logs from a Ruby on Rails application to Axiom using the Faraday library.'
 overview: 'Server-side web application framework written in Ruby'
 sidebarTitle: Ruby on Rails
 keywords: ['guides', 'ruby on rails', 'faraday']
 logoId: 'ruby'
@@ -11,14 +11,13 @@
 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 application 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 application logs effectively.
 
 <Prerequisites />
-{/* list separator */}
 - Install a [Ruby version manager](https://www.ruby-lang.org/en/documentation/installation/) like `rbenv` and use it to install the latest Ruby version.
 - Install [Ruby on Rails](https://guides.rubyonrails.org/v5.0/getting_started.html) using the `gem install rails` command.
 
 ## Set up the Ruby on Rails application

 1. Create a new Rails app using the `rails new myapp` command.


diff --git a/process-data/flows.mdx b/process-data/flows.mdx
@@ -12,7 +12,6 @@
 A flow is a way to filter, shape, and route data from an Axiom dataset to a destination that you choose. This page explains how to set up a flow.
 
 <Prerequisites />
-{/* list separator */}
 - Set up a destination. For more information, see [Destinations](/process-data/destinations).
 
 ## Set up a flow configuration
@@ -34,7 +33,7 @@
    <Note>
    If you only specify the name of the dataset in the query, Axiom routes all events to the destination.

    In the APL query, you can only use filters (such as `where` and `search`) and column transformations (such as `project` and `extend`).
    </Note>

 1. Click **Preview** to check whether the query you specified transforms your data as desired. The **Input event** section displays the original data stored in Axiom. The **Output event** section displays the transformed data that Axiom sends to the destination. The original data in the Axiom dataset isn’t affected by the transformation.
@@ -68,3 +67,3 @@

 ### Delivery rate of continuous flows


diff --git a/query-data/annotate-charts.mdx b/query-data/annotate-charts.mdx
@@ -20,7 +20,6 @@ Annotating charts lets you add context to your charts. For example, use annotati
 This adds context to the trends displayed in your charts and makes it easier to investigate issues in your app or system.
 
 <Prerequisites />
-{/* list separator */}
 - [Send data](/send-data/ingest) to your Axiom dataset.
 - [Create an API token in Axiom](/reference/tokens) with permissions to create, read, update, and delete annotations.
 

diff --git a/send-data/aws-firehose.mdx b/send-data/aws-firehose.mdx
@@ -17,7 +17,6 @@ Amazon Data Firehose is a service for delivering real-time streaming data to dif
 <AwsDisclaimer />
 
 <Prerequisites />
-{/* list separator */}
 - [Create an account on AWS Cloud](https://signin.aws.amazon.com/signup?request_type=register).
 
 ## Setup

diff --git a/send-data/aws-iot-rules.mdx b/send-data/aws-iot-rules.mdx
@@ -15,7 +15,6 @@ import ReplaceDatasetToken from "/snippets/replace-dataset-token.mdx"
 <AwsDisclaimer />
 
 <Prerequisites />
-{/* list separator */}
 - Create an AWS account with permissions to create and manage IoT rules, Lambda functions, and IAM roles.
 
 ## Create AWS Lambda function

diff --git a/send-data/aws-lambda.mdx b/send-data/aws-lambda.mdx
@@ -30,7 +30,6 @@ Axiom detects the extension and provides you with quick filters and a dashboard.
 </Note>
 
 <Prerequisites />
-{/* list separator */}
 - [Create an account on AWS Cloud](https://signin.aws.amazon.com/signup?request_type=register).
 
 ## Setup
@@ -91,6 +90,7 @@ Choose one of the following to install the Axiom Lambda Extension with Terraform
 - Use plain Terraform code
 
 <Accordion title="Example with plain Terraform code">
+
 ```tf
 resource "aws_lambda_function" "test_lambda" {
   filename      = "lambda_function_payload.zip"
@@ -116,16 +116,19 @@ resource "aws_lambda_function" "test_lambda" {
 }
 ```
 
-- Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
-- Replace `ARCH` with the system architecture type. For example, `arm64`.
-- Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
-{/* list separator */}
+<Info>
+Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
+Replace `ARCH` with the system architecture type. For example, `arm64`.
+Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
 <ReplaceDatasetToken />
+</Info>
+
 </Accordion>
 
 - Use the [AWS Lambda Terraform module](https://registry.terraform.io/modules/terraform-aws-modules/lambda/aws/latest)
 
 <Accordion title="Example with AWS Lambda Terraform module">
+
 ```tf
 module "lambda_function" {
   source = "terraform-aws-modules/lambda/aws"
@@ -148,11 +151,13 @@ module "lambda_function" {
 }
 ```
 
-- Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
-- Replace `ARCH` with the system architecture type. For example, `arm64`.
-- Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
-{/* list separator */}
+<Info>
+Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
+Replace `ARCH` with the system architecture type. For example, `arm64`.
+Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
 <ReplaceDatasetToken />
+</Info>
+
 </Accordion>
 
 You have installed the Axiom Lambda Extension. Go to the Axiom UI and ensure your dataset receives events properly.
@@ -167,9 +172,11 @@ Add a new layer to your Lambda function with the following ARN (Amazon Resource
 arn:aws:lambda:AWS_REGION:694952825951:layer:axiom-extension-ARCH:VERSION
 ```
 
-- Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
-- Replace `ARCH` with the system architecture type. For example, `arm64`.
-- Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
+<Info>
+Replace `AWS_REGION` with the AWS Region to send the request to. For example, `us-west-1`.
+Replace `ARCH` with the system architecture type. For example, `arm64`.
+Replace `VERSION` with the latest version number specified on the [GitHub Releases](https://github.com/axiomhq/axiom-lambda-extension/releases) page. For example, `11`.
+</Info>
 
 </Step>
 <Step>

diff --git a/send-data/aws-s3.mdx b/send-data/aws-s3.mdx
@@ -15,7 +15,6 @@ This page explains how to set up an AWS Lambda function to send logs from an S3
 <AwsDisclaimer />
 
 <Prerequisites />
-{/* list separator */}
 - Create an AWS account with permissions to create and manage S3 buckets, Lambda functions, and IAM roles. For more information, see the [AWS documentation](https://docs.aws.amazon.com/lambda/latest/dg/with-s3-example.html).
 
 ## Package the requests module

diff --git a/send-data/cloudfront.mdx b/send-data/cloudfront.mdx
@@ -19,7 +19,6 @@ Use the Axiom CloudFront Lambda to send CloudFront logs to Axiom using AWS S3 bu
 </Note>
 
 <Prerequisites />
-{/* list separator */}
 - [Create an account on AWS Cloud](https://signin.aws.amazon.com/signup?request_type=register).
 
 ## Setup

diff --git a/send-data/cloudwatch.mdx b/send-data/cloudwatch.mdx
@@ -29,7 +29,6 @@ Axiom CloudWatch Forwarder includes templates for the following CloudFormation s
 </Note>
 
 <Prerequisites />
-{/* list separator */}
 - [Create an account on AWS Cloud](https://signin.aws.amazon.com/signup?request_type=register).
 
 ## Installation

diff --git a/send-data/convex.mdx b/send-data/convex.mdx
@@ -13,7 +13,6 @@ Convex lets you manage the backend of your app (database, server, and more) from
 import Prerequisites from "/snippets/standard-prerequisites.mdx"
 
 <Prerequisites />
-{/* list separator */}
 - [Create a Convex account](https://www.convex.dev/login).
 - Set up your app with Convex. For example, follow one of the quickstart guides in the [Convex documentation](https://docs.convex.dev/quickstarts).
 

diff --git a/send-data/fluent-bit.mdx b/send-data/fluent-bit.mdx
@@ -16,7 +16,6 @@ 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.
 
 <Prerequisites />
-{/* list separator */}
 - [Install Fluent Bit](https://docs.fluentbit.io/manual/installation/getting-started-with-fluent-bit).
 
 ## Configure Fluent Bit

diff --git a/send-data/logstash.mdx b/send-data/logstash.mdx
@@ -20,7 +20,6 @@ It can read data from various `input` sources, filter data for the specified con
 Logstash sits between your data and where you want to keep it.
 
 <Prerequisites />
-{/* list separator */}
 - Visit the [Logstash download page](https://www.elastic.co/downloads/logstash) to install Logstash on your system.
 
 ## Configuration

diff --git a/send-data/nextjs.mdx b/send-data/nextjs.mdx
@@ -42,7 +42,6 @@ For information on the Axiom Vercel app and migrating from the Vercel app to the
 The rest of this page explains how to send data from your Next.js app to Axiom using the next-axiom or the @axiomhq/nextjs library.
 
 <Prerequisites />
-{/* list separator */}
 - [A new or existing Next.js app](https://nextjs.org/).
 
 ## Use next-axiom library

diff --git a/send-data/react.mdx b/send-data/react.mdx
@@ -22,7 +22,6 @@ This page explains how to use the @axiomhq/react library to send data from your
 </Note>
 
 <Prerequisites />
-{/* list separator */}
 - A new or existing React app.
 
 ## Install @axiomhq/react library

diff --git a/send-data/render.mdx b/send-data/render.mdx
@@ -13,7 +13,6 @@ import Prerequisites from "/snippets/standard-prerequisites.mdx"
 Render is a unified cloud to build and run all your apps and websites. Axiom provides complete visibility into your Render projects, allowing you to monitor the behavior of your websites and apps.
 
 <Prerequisites />
-{/* list separator */}
 - [Create an account on Render](https://dashboard.render.com/login).
 
 ## Setup

diff --git a/send-data/vector.mdx b/send-data/vector.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Send data from Vector to Axiom'
 description: 'This step-by-step guide will help you configure Vector to read and collect metrics from your sources using the Axiom sink.'
 overview: 'High-performance observability data pipeline'
 sidebarTitle: Vector
 keywords: ['vector', 'axiom documentation', 'documentation', 'axiom', 'guide', 'vector sink', 'docker logs', 'kubernetes logs', 'aws s3 logs', 'kafka logs']
@@ -34,7 +34,7 @@
 
 Send data to Axiom with Vector using the [`file` method](https://vector.dev/docs/reference/configuration/sources/file/) and the [`axiom` sink](https://vector.dev/docs/reference/configuration/sinks/axiom/).
 
-The example below configures Vector to read and collect logs from files and send them to Axiom:
+The example below configures Vector to read and collect logs from files and send them to Axiom.
 
 1. Create a vector configuration file `vector.toml` with the following content:
 
@@ -50,12 +50,12 @@
     dataset = "DATASET_NAME"
     ```
 
-1. In the code above, replace the following:
-    - Replace `VECTOR_SOURCE_ID` with the Vector source ID.
-    - Replace `PATH_TO_LOGS` with the path to the log files. For example, `/var/log/**/*.log`.
-    - Replace `SINK_ID` with the sink ID.
-    {/* list separator */}
+    <Info>
+    Replace `VECTOR_SOURCE_ID` with the Vector source ID.
+    Replace `PATH_TO_LOGS` with the path to the log files. For example, `/var/log/**/*.log`.
+    Replace `SINK_ID` with the sink ID.
     <ReplaceDatasetToken />
+    </Info>
 
 1. Run Vector to send logs to Axiom.
 
@@ -82,9 +82,10 @@
 dataset = "DATASET_NAME"
 ```
 
-- Replace `FIELD_TO_REMOVE` with the field you want to remove.
-{/* list separator */}
+<Info>
+Replace `FIELD_TO_REMOVE` with the field you want to remove.
 <ReplaceDatasetToken />
+</Info>
 
 <Note>
 Any changes to Vector’s `file` method can make the code example above outdated. If this happens, please refer to the [official Vector documentation on the `file` method](https://vector.dev/docs/reference/configuration/sources/file/), and we kindly ask you to inform us of the issue using the feedback tool at the bottom of this page.