Gathering detailed insights and metrics for next-axiom
Gathering detailed insights and metrics for next-axiom
Installations
npm install next-axiomDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Min. Node Version
>=18
Node Version
22.17.0
NPM Version
10.9.2
Releases
40
Languages
2
TypeScript
Nix
TypeScript (99.79%)
Nix (0.21%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
402 Stars
624 Commits
32 Forks
4 Watchers
35 Branches
27 Contributors
Updated on Jul 13, 2025
Maintainers
1
Package Meta Information
Latest Version
1.9.2
Package Id
next-axiom@1.9.2
Unpacked Size
301.28 kB
Size
83.56 kB
File Count
110
NPM Version
10.9.2
Node Version
22.17.0
Published on
Jul 13, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
3
next-axiom
Axiom unlocks observability at any scale.
- Ingest with ease, store without limits: Axiom’s next-generation datastore enables ingesting petabytes of data with ultimate efficiency. Ship logs from Kubernetes, AWS, Azure, Google Cloud, DigitalOcean, Nomad, and others.
- Query everything, all the time: Whether DevOps, SecOps, or EverythingOps, query all your data no matter its age. No provisioning, no moving data from cold/archive to “hot”, and no worrying about slow queries. All your data, all. the. time.
- Powerful dashboards, for continuous observability: Build dashboards to collect related queries and present information that’s quick and easy to digest for you and your team. Dashboards can be kept private or shared with others, and are the perfect way to bring together data from different sources.
For more information, check out the official documentation.
Introduction
This library allows you to send Web Vitals as well as structured logs from your Next.js application to Axiom.
Using the Pages Router? Use version
0.*which continues to receive security patches. Here's the README for0.x.
Prerequisites
- Create an Axiom account.
- Create a dataset in Axiom where you send your data.
- Create an API token in Axiom with permissions to create, read, update, and delete datasets.
- A new or existing Next.js app.
Install next-axiom
- In your terminal, go to the root folder of your Next.js app, and then run
npm install --save next-axiomto install the latest version of next-axiom. - Add the following environment variables to your Next.js app. For more information, see the Vercel documentation.
NEXT_PUBLIC_AXIOM_DATASETis the name of the Axiom dataset where you want to send data.NEXT_PUBLIC_AXIOM_TOKENis the Axiom API token you have generated.
- In the
next.config.tsfile, wrap your Next.js configuration inwithAxiom:
1const { withAxiom } = require('next-axiom'); 2 3module.exports = withAxiom({ 4 // Your existing configuration. 5});
Capture traffic requests
To capture traffic requests, create a middleware.ts file in the root folder of your Next.js app:
1import { Logger } from 'next-axiom' 2import { NextResponse } from 'next/server' 3import type { NextFetchEvent, NextRequest } from 'next/server' 4 5export async function middleware(request: NextRequest, event: NextFetchEvent) { 6 const logger = new Logger({ source: 'middleware' }); // traffic, request 7 logger.middleware(request) 8 9 event.waitUntil(logger.flush()) 10 return NextResponse.next() 11 12// For more information, see Matching Paths below 13export const config = { 14}
logger.middleware accepts a configuration object as the second argument. This object can contain the following properties:
logRequestDetails: Accepts a boolean or an array of keys. If you passtrue, it will add all the request details to the log (method, URL, headers, etc.). If you pass an array of strings, it will only add the specified keys. See Request and NextRequest for documentation on the available keys. IflogRequestDetailsis enabled the function will return a Promise that needs to be awaited.
1export async function middleware(request: NextRequest, event: NextFetchEvent) { 2 const logger = new Logger({ source: "middleware" }); 3 await logger.middleware(request, { logRequestDetails: ["body", "nextUrl"] }); 4 5 event.waitUntil(logger.flush()); 6 return NextResponse.next(); 7}
Web Vitals
To send Web Vitals to Axiom, add the AxiomWebVitals component from next-axiom to the app/layout.tsx file:
1import { AxiomWebVitals } from 'next-axiom'; 2 3export default function RootLayout() { 4 return ( 5 <html> 6 ... 7 <AxiomWebVitals /> 8 <div>...</div> 9 </html> 10 ); 11}
Web Vitals are only sent from production deployments.
Logs
Send logs to Axiom from different parts of your app. Each log function call takes a message and an optional fields object.
1log.debug('Login attempt', { user: 'j_doe', status: 'success' }); // Results in {"message": "Login attempt", "fields": {"user": "j_doe", "status": "success"}} 2log.info('Payment completed', { userID: '123', amount: '25USD' }); 3log.warn('API rate limit exceeded', { endpoint: '/users/1', rateLimitRemaining: 0 }); 4log.error('System Error', { code: '500', message: 'Internal server error' });
Route handlers
Wrap your route handlers in withAxiom to add a logger to your request and log exceptions automatically:
1import { withAxiom, AxiomRequest } from 'next-axiom'; 2 3export const GET = withAxiom((req: AxiomRequest) => { 4 req.log.info('Login function called'); 5 6 // You can create intermediate loggers 7 const log = req.log.with({ scope: 'user' }); 8 log.info('User logged in', { userId: 42 }); 9 10 return NextResponse.json({ hello: 'world' }); 11});
Route handlers accept a configuration object as the second argument. This object can contain the following properties:
-
logRequestDetails: Accepts a boolean or an array of keys. If you passtrue, it will add all the request details to the log (method, URL, headers, etc.). If you pass an array of strings, it will only add the specified keys. See Request and NextRequest for documentation on the available keys. -
NotFoundLogLevel: Override the log level for NOT_FOUND errors. Defaults towarn. -
RedirectLogLevel: Override the log level for NEXT_REDIRECT errors. Defaults toinfo.
Config example:
1export const GET = withAxiom( 2 async () => { 3 return new Response("Hello World!"); 4 }, 5 { 6 logRequestDetails: ['body', 'nextUrl'], // { logRequestDetails: true } is also valid 7 NotFoundLogLevel: 'error', 8 RedirectLogLevel: 'debug', 9 } 10);
Client components
To send logs from client components, add useLogger from next-axiom to your component:
1'use client'; 2import { useLogger } from 'next-axiom'; 3 4export default function ClientComponent() { 5 const log = useLogger(); 6 log.debug('User logged in', { userId: 42 }); 7 return <h1>Logged in</h1>; 8}
Server components
To send logs from server components, add Logger from next-axiom to your component, and call flush before returning:
1import { Logger } from 'next-axiom'; 2 3export default async function ServerComponent() { 4 const log = new Logger(); 5 log.info('User logged in', { userId: 42 }); 6 7 // ... 8 9 await log.flush(); 10 return <h1>Logged in</h1>; 11}
Log levels
The log level defines the lowest level of logs sent to Axiom. Choose one of the following levels (from lowest to highest):
debugis the default setting. It means that you send all logs to Axiom.infowarnerrormeans that you only send the highest-level logs to Axiom.offmeans that you don't send any logs to Axiom.
For example, to send all logs except for debug logs to Axiom:
1export NEXT_PUBLIC_AXIOM_LOG_LEVEL=info
Capture errors
To capture routing errors, use the error handling mechanism of Next.js:
- Go to the
appfolder. - Create an
error.tsxfile. - Inside your component function, add
useLoggerfrom next-axiom to send the error to Axiom. For example:
1"use client";
2
3import { useLogger, LogLevel } from "next-axiom";
4import { usePathname } from "next/navigation";
5
6export default function ErrorPage({
7 error,
8}: {
9 error: Error & { digest?: string };
10}) {
11 const pathname = usePathname()
12 const log = useLogger({ source: "error.tsx" });
13 let status = error.message == 'Invalid URL' ? 404 : 500;
14
15 log.logHttpRequest(
16 LogLevel.error,
17 error.message,
18 {
19 host: window.location.href,
20 path: pathname,
21 statusCode: status,
22 },
23 {
24 error: error.name,
25 cause: error.cause,
26 stack: error.stack,
27 digest: error.digest,
28 },
29 );
30
31 return (
32 <div className="p-8">
33 Ops! An Error has occurred:{" "}
34 <p className="text-red-400 px-8 py-2 text-lg">`{error.message}`</p>
35 <div className="w-1/3 mt-8">
36 <NavTable />
37 </div>
38 </div>
39 );
40}Upgrade to the App Router
next-axiom switched to support the App Router starting with version 1.0. If you are upgrading a Pages Router app with next-axiom v0.x to the App Router, you will need to make the following changes:
- Upgrade next-axiom to version 1.0.0 or higher
- Make sure that exported variables has
NEXT_PUBLIC_prefix, e.g:NEXT_PUBLIC_AXIOM_TOKEN - Use
useLoggerhook in client components instead oflogprop - For server side components, you will need to create an instance of
Loggerand flush the logs before component returns. - For web-vitals, remove
reportWebVitals()and instead add theAxiomWebVitalscomponent to your layout.
FAQ
How can I send logs from Vercel preview deployments?
The Axiom Vercel integration sets up an environment variable called NEXT_PUBLIC_AXIOM_INGEST_ENDPOINT, which by default is only enabled for the production environment. To send logs from preview deployments, go to your site settings in Vercel and enable preview deployments for that environment variable.
How can I extend the logger?
You can use log.with to create an intermediate logger, for example:
1const logger = userLogger().with({ userId: 42 }); 2logger.info('Hi'); // will ingest { ..., "message": "Hi", "fields" { "userId": 42 }}
License
Distributed under the MIT License.
No vulnerabilities found.
No security vulnerabilities found.