LoginSign Up
← Back to all sparks
A

Apache SkyWalking

ANALYTICS
Velocity3.8

Observability platform for distributed systems and microservices

skywalking.apache.org ↗

SkyWalking 11.1 builds service maps from OpenTelemetry traces, no SkyWalking agent required.

observabilityopentelemetryapmbanyandbtopology
◆Current state
Apache SkyWalking spent 2025 and 2026 rebuilding its foundations: BanyanDB replaced H2, the Groovy DSL runtime gave way to ANTLR4 and Javassist, and 11.0.0 split the UI out of the backend. Version 11.1.0, released November 6, stores OTLP traces as they arrive and adds a Trace Analysis Language that turns spans into service, instance and endpoint metrics, topology and dashboards for the databases, caches and queues those services call. Applications instrumented only with OpenTelemetry SDKs now get SkyWalking's dashboards without its agent.
◆Where it's heading
After taking storage and runtime in-house, SkyWalking is opening its front door to OpenTelemetry data. Its value is shifting from its own agents toward the analysis it runs on any trace source.
◆Prediction
Expect more TAL coverage and OpenTelemetry quick starts, with SkyWalking's own agents positioned as optional rather than required.

◆Recent moves

  1. 7d ago

    11.1.0 - Metrics and Topology from OTLP Traces

    ⚡ SPARK

    The rebuild of storage and runtime now pays off at the input side: OTLP traces are stored natively and turned into metrics and topology by the new Trace Analysis Language. It moves SkyWalking from an agent-led APM toward an analysis backend for any OpenTelemetry-instrumented app.

    View source ↗
  2. 2mo ago

    11.0.0 - Horizon Ready, Runtime Rule Hot-Update and Live DSL Debugger

    ⚡ SPARK

    The third structural removal in three releases, and the largest: after taking storage and the DSL runtime in-house, SkyWalking pushes the UI out. It arrives alongside the operational hardening — TLS on every REST server with hot-reload, a real alarm query API — that a decoupled backend needs to stand on its own.

    View source ↗
  3. 7mo ago

    10.4.0 - GenAI Observability, Groovy-Free Runtime and Grafana Tempo Compatible

    ⚡ SPARK

    10.4.0 pairs a new telemetry domain — GenAI observability — with an OAL V2 engine that replaces string-based filters and Groovy-era behaviour with immutable ASTs, typed enums and precise error locations. Grafana Tempo compatibility opens it to teams already standardised elsewhere.

    View source ↗
  4. 10mo ago

    10.3.0 - New Trace Model in BanyanDB

    A new trace model in BanyanDB, presented with deployment evidence at around 200 services. This is the release where SkyWalking's own storage engine is claimed to be ready for large-scale use rather than being the experimental option.

    View source ↗
  5. 1y ago

    10.2.0 - No H2, More BanyanDB

    ⚡ SPARK

    10.2.0 removed H2 storage permanently and added BanyanDB 0.8.0 support, closing off the easy default that small deployments relied on. It also added doc_values only for Elasticsearch fields that need sorting or aggregation.

    View source ↗