Datadog

​

Setup

1. Create an API key in Organization Settings → API Keys.
2. Set the environment variables:

DD_API_KEY=your-api-key
DD_SITE=datadoghq.com # or datadoghq.eu, us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com
DD_SERVICE=my-api

3. Wire the transport:

import { Elysia } from 'elysia'
import logixlysia from 'logixlysia'
import { createDatadogTransport } from 'logixlysia/datadog'

const app = new Elysia()
  .use(
    logixlysia({
      config: {
        transports: [createDatadogTransport()]
      }
    })
  )
  .get('/', () => 'ok')
  .listen(3000)

4. Trigger a request and open Logs → Explorer in Datadog.

​

Environment Variables

​

Options

const datadog = createDatadogTransport({
  service: 'my-api',
  tags: { env: 'production', team: 'backend' }
})

​

Payload

• status — the log level lowercased (info, warning, error), which Datadog’s default status remapper picks up for severity coloring.
• http.status_code — the HTTP response status from access logs, following Datadog’s standard attribute so response-code facets work out of the box.
• Attributes — the full meta object rides along nested (request.method, context.requestId, durationMs, …), searchable with @request.method:GET style queries.

​

Troubleshooting

• 403 — the API key is invalid, or it belongs to a different site than DD_SITE; keys are region-scoped.
• Wrong region — EU organizations must set DD_SITE=datadoghq.eu; a wrong site surfaces as a non-2xx response through the onError hook or stderr.
• Levels look wrong — if you customized the status remapper in a log pipeline, map it to the status attribute.