Skip to main content
← Back to Changelog
NEW FEATURE

Fleet management in Beta

Fleet changes what your OpenTelemetry Collectors and applications collect, and where they send it, from Pydantic Logfire. You don't edit config files on each machine or redeploy. Fleet is in Beta and on for every plan.

Changing an SDK policy in Fleet: Minimum log level is set to Warn, the review shows Log levels going from Application controlled to Warn and above, the policy is published, and checkout-api then shows Warn and above as both the policy and the running setting

Collectors and SDKs connect to Fleet over OpAMP, the OpenTelemetry standard for managing telemetry software. Each one reports its health, the policy it runs, and whether that policy applied. Fleet carries settings, not telemetry: your data keeps its existing path and write token.

  • Hosts. logfire-cli collector install sets up an OpenTelemetry Collector as a service on Linux, macOS or Windows, under the OpAMP Supervisor, and joins it to your project with a one-time enrollment key.
  • Kubernetes. A small bridge drives the OpenTelemetry Operator, so your Collectors stay standard OpenTelemetryCollector resources.
  • Existing Collectors. Add Collector › Existing Collector gives you a connection key and a snippet for the opamp extension in Collector Contrib. A Collector you manage with Helm or GitOps then shows in Fleet with its health, components and configuration, as Report only: its configuration stays yours.

Python, Node.js, Java, .NET and Go applications connect with a small package. On the Logfire SDK it's one option. In Python, on Logfire 5.5.0 and Python 3.11+:

pip install --upgrade 'logfire[fleet]'

import logfire

logfire.configure(service_name='checkout-api', fleet=True)

LOGFIRE_FLEET=true does the same without a code change. In Node.js, on @pydantic/logfire-node 0.22.0:

npm install @pydantic/logfire-node @pydantic/logfire-fleet-otel

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

logfire.configure({ serviceName: 'checkout-api', fleet: true })

Both read the Fleet server and connection key from OTEL_OPAMP_ENDPOINT and OTEL_OPAMP_HEADERS. Plain OpenTelemetry SDKs connect through logfire-fleet-otel packages for each language.

A policy is a versioned set of settings you publish from Logfire. A Collector policy holds the whole pipeline. An SDK policy sets trace sampling, sampling rules, minimum log level, signal exports, volume controls, attribute redaction and scrubbing, and leaves everything else to the application. In Python, Node.js, Java and .NET, the SDK policy covers every exporter the SDK sends through, the console included, so redaction and sampling hold for every destination.

Review shows each change against the published version. A host Collector or application that can't run a version refuses it and keeps its configuration. Turn on rollouts (in early access now) to try a version on a pilot group first, and restore any past version to roll back.

Read the launch post: Manage your telemetry in Logfire, send it anywhere.

Where to find it: Fleet management in your project sidebar. See the Fleet docs.