iCreatAI News
Back to main site
Skip to content
Trending storyPast story

Logfire launches Fleet Management beta

3 reports1 sources3 days agoUpdated

Understand this story

AI overview

Pydantic Logfire releases Fleet Management (Beta), available on all plans. Users can centrally modify, within Logfire, what data the OpenTelemetry Collector and Python, Node.js, Java, .NET, and Go application SDKs collect and where they send it, without changing configuration files or redeploying; the plan determines the number of applications and Collector policies Fleet can manage, and usage is displayed in real time. Logfire explains that while the service is running continuously, log levels, attribute redaction, and sampling rates can also be adjusted remotely, with policies taking effect within seconds of being published; in the example, checkout-api sets the minimum log level to Warn, masks sensitive attributes with *token*, lowers the sampling rate to 10%, and drops the /health* rule. Onboarding requires a Logfire project, a write token, Python 3.11 or later, and uv. The rollout feature in early access lets new versions be pushed first to a designated pilot group. Collectors managed by Helm or GitOps appear in Fleet in a "report-only" state, showing health status, components, and configuration; Fleet does not modify the configuration of such Collectors. The Logfire team also used a black-box conformance test suite to test the upstream OpenTelemetry OpAMP clients, reporting that it found multiple specification deviations in the Collector's OpAMP extension and Supervisor as well as in the Java, Python, and .NET clients, and has reported them for fixes.

AI overview based on source reports · Updated 3 days ago

Latest developmentNov 11 17:00
Pydantic Logfire team tests OpAMP clients in practice: finds multiple specification deviations in upstream OpenTelemetry clients

Developments

3 developments

  1. Nov 11 17:00 · 1 reports
    Pydantic shares how the OpAMP client core is built and tested
    Pydantic AI Articles：What we found testing OpAMP clients against the spec
  2. Nov 10 17:00 · 1 reports
    Introducing online adjustment of log levels, redaction, and sampling with Fleet
    Pydantic AI Articles：Turn down OpenTelemetry noise without a redeploy
  3. Nov 9 17:00 · 1 reports
    Pydantic Logfire launches Fleet Management beta
    Pydantic AI Articles：Manage your telemetry in Logfire, send it anywhere

Coverage timeline

Follow the coverage to explore different perspectives.

Nov 11
  1. Pydantic AI Articles
    What we found testing OpAMP clients against the spec

    Pydantic describes how its Logfire Fleet Management OpAMP clients for Rust, Go, Node.js, Python, Java and .NET share one Rust protocol core, run as WebAssembly or a native library, and are checked against roughly 300 normative spec statements, TLA+ models, Kani and Verus proofs, black-box conformance and fault testing. Running the same scenarios against upstream OpenTelemetry clients surfaced bugs in the Collector's OpAMP extension and Supervisor and in the Java, Python and .NET clients, including instance UID handling, reconnect and status reporting, capability declarations and startup panics, plus one critical security vulnerability that the core is not affected by.

Nov 10
  1. Pydantic AI Articles
    Turn down OpenTelemetry noise without a redeploy

    Pydantic Logfire's Fleet Management lets you connect a service and its host Collector via OpAMP and change log level, attribute redaction and trace sampling while both keep running. The post walks through a FastAPI app with fleet=True, publishing SDK policies to drop debug logs, mask *token* attributes and sample 10% of traces, plus installing a host Collector and adding nginx logs. It also covers early-access rollouts, Kubernetes and existing Collectors, and troubleshooting.

Nov 9
  1. Pydantic AI Articles
    Manage your telemetry in Logfire, send it anywhere

    Pydantic Logfire has launched Fleet Management in Beta on every plan, letting users change what their OpenTelemetry Collectors and application SDKs collect and where they send it from Logfire, without editing config files or redeploying apps. Clients connect over OpAMP and pick up published, versioned policies within seconds, covering settings such as sampling, minimum log level, attribute redaction and scrubbing across all exporters the SDK exports through. Supported targets include host Collectors, Kubernetes clusters via the OpenTelemetry Operator, existing Collectors through the opamp extension, and Python, Node.js, Java, .NET and Go applications.

Activity for this story

Current comparable activity
3
Peak comparable activity
10Nov 10 17:00
Change in the past 24 hours
-49%

Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.