Claude Code for Axiom: Serverless Observability and Log Analytics — Claude Skills 360 Blog
Blog / AI / Claude Code for Axiom: Serverless Observability and Log Analytics
AI

Claude Code for Axiom: Serverless Observability and Log Analytics

Published: July 18, 2027
Read time: 5 min read
By: Claude Skills 360

Axiom provides serverless log analytics and observability — new Axiom({ token: apiKey }) initializes the client. axiom.ingest("dataset", [{ ...fields }]) sends structured log events; axiom.flush() batches and drains the queue. Query with APL (Axiom Processing Language): axiom.query("['my-dataset'] | where status >= 400 | summarize count() by bin_auto(timestamp), route") returns time-series results. APL is Kusto-inspired: | where, | project, | summarize, | extend, | top N by, | order by, | join, | union. axiom.queryLegacy(dataset, { apl: query }) for the datasets API. OpenTelemetry: new OTLPTraceExporter({ url: "https://api.axiom.co/v1/traces", headers: { Authorization: "Bearer TOKEN", "X-Axiom-Dataset": "my-traces" } }) exports spans. @axiomhq/winston and @axiomhq/pino are logging transport plugins. Vercel integration: add Axiom as a Log Drain in the Vercel dashboard — all function logs flow to Axiom automatically. axiom.datasets.create(name) and axiom.datasets.list() manage datasets. Claude Code generates Axiom structured logging, APL analytics queries, and OpenTelemetry tracing pipelines.

CLAUDE.md for Axiom

## Axiom Stack
- Version: @axiomhq/js >= 1.x
- Init: const axiom = new Axiom({ token: process.env.AXIOM_TOKEN! })
- Ingest: axiom.ingest("my-dataset", [{ timestamp: new Date().toISOString(), level: "info", message, ...context }])
- Flush: await axiom.flush() — required at Worker/Edge function end (no long-lived process)
- APL query: const result = await axiom.query("['my-dataset'] | where level == 'error' | order by timestamp desc | limit 100")
- Result rows: result.matches — [{ _time, data: Record<string, unknown> }]
- Winston transport: createTransport({ token, dataset }) from @axiomhq/winston

Axiom Client

// lib/axiom/client.ts — structured logging and analytics with Axiom
import { Axiom } from "@axiomhq/js"

export const axiom = new Axiom({
  token: process.env.AXIOM_TOKEN!,
  ...(process.env.AXIOM_ORG_ID ? { orgId: process.env.AXIOM_ORG_ID } : {}),
})

const DATASET = process.env.AXIOM_DATASET ?? "app-logs"

export type LogLevel = "debug" | "info" | "warn" | "error"

export type LogContext = {
  traceId?:     string
  spanId?:      string
  userId?:      string
  sessionId?:   string
  route?:       string
  method?:      string
  statusCode?:  number
  durationMs?:  number
  [key: string]: unknown
}

/** Structured logger — always includes timestamp and level */
export const logger = {
  debug: (message: string, ctx: LogContext = {}) =>
    log("debug", message, ctx),

  info: (message: string, ctx: LogContext = {}) =>
    log("info", message, ctx),

  warn: (message: string, ctx: LogContext = {}) =>
    log("warn", message, ctx),

  error: (message: string, err?: Error | unknown, ctx: LogContext = {}) => {
    const errCtx = err instanceof Error
      ? { errorName: err.name, errorMessage: err.message, errorStack: err.stack }
      : { error: String(err) }
    return log("error", message, { ...errCtx, ...ctx })
  },

  flush: () => axiom.flush(),
}

function log(level: LogLevel, message: string, ctx: LogContext) {
  const event = {
    timestamp: new Date().toISOString(),
    level,
    message,
    service: process.env.SERVICE_NAME ?? "app",
    env: process.env.NODE_ENV ?? "development",
    ...ctx,
  }

  axiom.ingest(DATASET, [event])
  // Mirror to console in dev
  if (process.env.NODE_ENV !== "production") {
    const fn = level === "error" ? console.error : level === "warn" ? console.warn : console.log
    fn(`[${level.toUpperCase()}] ${message}`, ctx)
  }
}

// ── APL query helpers ──────────────────────────────────────────────────────

export type QueryResult = {
  rows: Record<string, unknown>[]
  elapsed: number
}

export async function apl(query: string): Promise<QueryResult> {
  const start = Date.now()
  const result = await axiom.query(query)
  return {
    rows: (result.matches ?? []).map((m) => ({ _time: m._time, ...m.data })),
    elapsed: Date.now() - start,
  }
}

export async function getErrorRate(
  route: string,
  hours = 24,
): Promise<Array<{ bin: string; errors: number; total: number; errorRate: number }>> {
  const { rows } = await apl(`
    ['${DATASET}']
    | where timestamp > ago(${hours}h)
    | where route == "${route}"
    | summarize
        errors = countif(level == "error"),
        total  = count()
      by bin_auto(timestamp)
    | extend errorRate = todouble(errors) / todouble(total) * 100
    | order by timestamp asc
  `)
  return rows as any
}

export async function getSlowRoutes(
  p99Ms = 1000,
  hours = 24,
): Promise<Array<{ route: string; p99: number; p95: number; count: number }>> {
  const { rows } = await apl(`
    ['${DATASET}']
    | where timestamp > ago(${hours}h)
    | where isnotnull(durationMs)
    | summarize
        p99   = percentile(durationMs, 99),
        p95   = percentile(durationMs, 95),
        count = count()
      by route
    | where p99 > ${p99Ms}
    | order by p99 desc
    | limit 20
  `)
  return rows as any
}

export async function recentErrors(limit = 50): Promise<Array<Record<string, unknown>>> {
  const { rows } = await apl(`
    ['${DATASET}']
    | where timestamp > ago(1h)
    | where level == "error"
    | order by timestamp desc
    | limit ${limit}
  `)
  return rows
}

Next.js Request Logging Middleware

// middleware.ts — instrument every request with Axiom
import { NextResponse } from "next/server"
import type { NextRequest } from "next/server"
import { logger } from "@/lib/axiom/client"
import { randomUUID } from "crypto"

export async function middleware(req: NextRequest) {
  const traceId = randomUUID()
  const start = Date.now()

  const res = NextResponse.next({
    request: {
      headers: new Headers({ ...Object.fromEntries(req.headers), "x-trace-id": traceId }),
    },
  })

  res.headers.set("x-trace-id", traceId)

  // Log after response
  const status = res.status
  const durationMs = Date.now() - start

  logger.info("http_request", {
    traceId,
    method: req.method,
    route: req.nextUrl.pathname,
    statusCode: status,
    durationMs,
    userAgent: req.headers.get("user-agent") ?? "",
    country: req.geo?.country ?? "",
  })

  await logger.flush() // Required for Edge — no persistent process
  return res
}

export const config = {
  matcher: ["/api/:path*", "/((?!_next|favicon).*)"],
}

OpenTelemetry Tracing

// lib/axiom/tracing.ts — OTel tracing exported to Axiom
import { NodeSDK } from "@opentelemetry/sdk-node"
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http"
import { Resource } from "@opentelemetry/resources"
import { SEMRESATTRS_SERVICE_NAME, SEMRESATTRS_SERVICE_VERSION } from "@opentelemetry/semantic-conventions"
import { SimpleSpanProcessor } from "@opentelemetry/sdk-trace-base"
import { HttpInstrumentation } from "@opentelemetry/instrumentation-http"

const exporter = new OTLPTraceExporter({
  url: "https://api.axiom.co/v1/traces",
  headers: {
    Authorization: `Bearer ${process.env.AXIOM_TOKEN}`,
    "X-Axiom-Dataset": process.env.AXIOM_TRACES_DATASET ?? "app-traces",
  },
})

export const sdk = new NodeSDK({
  resource: new Resource({
    [SEMRESATTRS_SERVICE_NAME]: process.env.SERVICE_NAME ?? "app",
    [SEMRESATTRS_SERVICE_VERSION]: process.env.npm_package_version ?? "0.0.0",
  }),
  spanProcessor: new SimpleSpanProcessor(exporter),
  instrumentations: [new HttpInstrumentation()],
})

// Call sdk.start() in instrumentation.ts (Next.js) or app startup
// import { trace } from "@opentelemetry/api"
// const tracer = trace.getTracer("my-service")
// const span = tracer.startSpan("database.query")
// span.setAttribute("db.statement", sql)
// span.end()

For the Sentry alternative when needing application error monitoring with stack trace capture, release tracking, session replay, performance monitoring with automatic instrumentation, and a debug-focused UI — Sentry is the gold standard for error tracking while Axiom is the tool when you need flexible structured log analytics with APL queries over your own event schema, see the Sentry guide. For the Datadog alternative when needing enterprise APM with distributed tracing, infrastructure metrics, anomaly detection, SLO tracking, and a managed SIEM — Datadog is a full-stack observability platform while Axiom is a cost-effective serverless log analytics layer that excels at storing and querying structured events from edge functions and serverless workloads, see the Datadog guide. The Claude Skills 360 bundle includes Axiom skill sets covering structured logging, APL analytics, and OTel tracing. Start with the free tier to try log analytics generation.

Keep Reading

AI

Claude Code for email.contentmanager: Python Email Content Accessors

Read and write EmailMessage body content with Python's email.contentmanager module and Claude Code — email contentmanager ContentManager for the class that maps content types to get and set handler functions allowing EmailMessage to support get_content and set_content with type-specific behaviour, email contentmanager raw_data_manager for the ContentManager instance that handles raw bytes and str payloads without any conversion, email contentmanager content_manager for the standard ContentManager instance used by email.policy.default that intelligently handles text plain text html multipart and binary content types, email contentmanager get_content_text for the handler that returns the decoded text payload of a text-star message part as a str, email contentmanager get_content_binary for the handler that returns the raw decoded bytes payload of a non-text message part, email contentmanager get_data_manager for the get-handler lookup used by EmailMessage get_content to find the right reader function for the content type, email contentmanager set_content text for the handler that creates and sets a text part correctly choosing charset and transfer encoding, email contentmanager set_content bytes for the handler that creates and sets a binary part with base64 encoding and optional filename Content-Disposition, email contentmanager EmailMessage get_content for the method that reads the message body using the registered content manager handlers, email contentmanager EmailMessage set_content for the method that sets the message body and MIME headers in one call, email contentmanager EmailMessage make_alternative make_mixed make_related for the methods that convert a simple message into a multipart container, email contentmanager EmailMessage add_attachment for the method that attaches a file or bytes to a multipart message, and email contentmanager integration with email.message and email.policy and email.mime and io for building high-level email readers attachment extractors text body accessors HTML readers and policy-aware MIME construction pipelines.

5 min read Feb 12, 2029
AI

Claude Code for email.charset: Python Email Charset Encoding

Control header and body encoding for international email with Python's email.charset module and Claude Code — email charset Charset for the class that wraps a character set name with the encoding rules for header encoding and body encoding describing how to encode text for that charset in email messages, email charset Charset header_encoding for the attribute specifying whether headers using this charset should use QP quoted-printable encoding BASE64 encoding or no encoding, email charset Charset body_encoding for the attribute specifying the Content-Transfer-Encoding to use for message bodies in this charset such as QP or BASE64, email charset Charset output_codec for the attribute giving the Python codec name used to encode the string to bytes for the wire format, email charset Charset input_codec for the attribute giving the Python codec name used to decode incoming bytes to str, email charset Charset get_output_charset for returning the output charset name, email charset Charset header_encode for encoding a header string using the charset's header_encoding method, email charset Charset body_encode for encoding body content using the charset's body_encoding, email charset Charset convert for converting a string from the input_codec to the output_codec, email charset add_charset for registering a new charset with custom encoding rules in the global charset registry, email charset add_alias for adding an alias name that maps to an existing registered charset, email charset add_codec for registering a codec name mapping for use by the charset machinery, and email charset integration with email.message and email.mime and email.policy and email.encoders for building international email senders non-ASCII header encoders Content-Transfer-Encoding selectors charset-aware message constructors and MIME encoding pipelines.

5 min read Feb 11, 2029
AI

Claude Code for email.utils: Python Email Address and Header Utilities

Parse and format RFC 2822 email addresses and dates with Python's email.utils module and Claude Code — email utils parseaddr for splitting a display-name plus angle-bracket address string into a realname and email address tuple, email utils formataddr for combining a realname and address string into a properly quoted RFC 2822 address with angle brackets, email utils getaddresses for parsing a list of raw address header strings each potentially containing multiple comma-separated addresses into a list of realname address tuples, email utils parsedate for parsing an RFC 2822 date string into a nine-tuple compatible with time.mktime, email utils parsedate_tz for parsing an RFC 2822 date string into a ten-tuple that includes the UTC offset timezone in seconds, email utils parsedate_to_datetime for parsing an RFC 2822 date string into an aware datetime object with timezone, email utils formatdate for formatting a POSIX timestamp or the current time as an RFC 2822 date string with optional usegmt and localtime flags, email utils format_datetime for formatting a datetime object as an RFC 2822 date string, email utils make_msgid for generating a globally unique Message-ID string with optional idstring and domain components, email utils decode_rfc2231 for decoding an RFC 2231 encoded parameter value into a tuple of charset language and value, email utils encode_rfc2231 for encoding a string as an RFC 2231 encoded parameter value, email utils collapse_rfc2231_value for collapsing a decoded RFC 2231 tuple to a Unicode string, and email utils integration with email.message and email.headerregistry and datetime and time for building address parsers date formatters message-id generators header extractors and RFC-compliant email construction utilities.

5 min read Feb 10, 2029

Put these ideas into practice

Claude Skills 360 gives you production-ready skills for everything in this article — and 2,350+ more. Start free or go all-in.

Back to Blog

Get 360 skills free