← Back to all sparks
P

Pinpoint

ANALYTICS
Velocity3.8

Open-source APM tool for monitoring large-scale distributed systems

Pinpoint 4.0 takes OpenTelemetry traces without its agent; 3.1.1 tames reactive overhead.

apmdistributed tracingopentelemetryjvm agentsobservability
◆Current state
Pinpoint, the open-source APM, opened its 4.0 line on 29 October: services on by default, OpenTelemetry traces ingested without the Pinpoint agent, and service-based alarms. A month earlier, 3.1.1 cut agent overhead on Reactor, WebFlux and Kotlin coroutine workloads, added Spring Framework 7 compatibility and hardened the Web and Batch modules, with no schema changes.
◆Where it's heading
Pinpoint is loosening the tie between its backend and its own Java agent, which widens who can send it data. The 3.x line keeps the agent fast on modern reactive stacks while 4.0 takes the platform changes, the same split between rare structural jumps and steady patch work seen across 3.0 and 3.1.
◆Prediction
Expect 4.0.x patches settling OpenTelemetry ingest and the services model, with 3.1.x receiving backports in parallel as 3.0.x did after 3.1.0.

◆Recent moves

  1. 7d ago

    4.0.0 release

    ⚡ SPARK

    Pinpoint 4.0 opens a new major line: services on by default, OpenTelemetry traces accepted without the Pinpoint agent, and service-based alarms. It changes how data is organised and what can feed it.

    View source ↗
  2. 1mo ago

    Pinpoint 3.1.1 cuts agent overhead on reactive Java apps

    3.1.1 removes megamorphic dispatch in the Reactor instrumentation on JDK 21/25, stops 'corrupted call stack' log storms on WebFlux services and adds Spring Framework 7 support. It upgrades in place from 3.1.0 and was the last 3.x release before 4.0.

    View source ↗
  3. 5mo ago

    3.1.0 rebuilds ServerMap and lifts application names to 254 characters

    ⚡ SPARK

    The first release in this window to change the platform rather than its plugin coverage: ServerMap becomes V3 with a redesigned storage layout, new query path and new map tables, and applicationName goes from 24 to 254 characters. Both require coordinated agent and collector upgrades, which is why the notes lead with a property you must add at agent start.

    View source ↗
  4. 7mo ago

    3.0.5: backports and a move to Central Portal publishing

    Entirely backports — agent interceptable targets, an S3 auth header, a gRPC plugin stream getter, span sender state init — plus a migration to Central Portal publishing. Maintenance for users staying on the 3.0 line.

    View source ↗
  5. 11mo ago

    3.0.4 adds Java 26, Kafka Streams and nested Spring Boot JAR support

    Runtime coverage widens where it matters for modern Java deployments: Java 26, Kafka Streams tracing behind a flag, and nested JAR filesystems as used by Spring Boot. Reactor tracing improves and collector CPU usage drops.

    View source ↗
  6. 1y ago

    3.0.3 adds an S3 client plugin and Kafka 4.x compatibility

    New plugin coverage for S3 clients and Kafka 4.x, plus Kafka entry-point and gRPC forwarding fixes. From 3.x, executables are published to Maven Central rather than distributed only as archives.

    View source ↗