Resource Attributes

Resource attributes describe the entity producing telemetry. Use them for stable metadata such as service namespace, deployment metadata, or an application instance identifier.

Node.js

import * as logfire from '@pydantic/logfire-node'

logfire.configure({
  serviceName: 'checkout-api',
  resourceAttributes: {
    'service.namespace': 'payments',
    'service.instance.id': process.env.HOSTNAME,
  },
})

Browser

Start with the frontendOptions generated under Frontend > Applications. The frontend application owns service.name, service.namespace, and the optional environment, so browser code should add only other stable attributes:

import * as logfire from '@pydantic/logfire-browser'

const frontendOptions = {
  baseUrl: '<generated-regional-base-url>',
  token: '<frontend-application-token>',
}

logfire.configureFrontend({
  ...frontendOptions,
  resourceAttributes: {
    'app.installation.id': '<stable-installation-id>',
  },
})

Precedence

With configure(), first-class options such as serviceName, serviceVersion, and environment take precedence over conflicting resource attributes. With browser configureFrontend(), serviceVersion is configurable; service name and environment belong to the frontend application.

In Node.js, values from OTEL_RESOURCE_ATTRIBUTES are also read by the OpenTelemetry SDK and can override code-level values depending on SDK configuration.

Do not use resource attributes for per-request values, user identifiers, or secrets. Put request-specific data on spans as attributes instead.