Download

https://skywalking.apache.org/downloads/

Notice

Don't download source codes from this page. Please follow build document, if you want to build source codes by yourself.

Project

• Move the DSL class-loading machinery under core/dsl. core/classloader held only DSL types — RuleClassLoader, DSLClassLoaderManager, ClassLoaderGc, UnloadProbePayload and BytecodeClassDefiner — so it is now core/dsl/classloader, and Catalog moves to core/dsl because a rule-file taxonomy is not a class-loading concern. Three copies of the "define a generated class into the right loader" dispatch (MAL, LAL, MeterSystem) collapse into a static BytecodeClassDefiner.define, which also gives the JDK 17 --add-opens rationale one home instead of four. Three of the four copies of the generated-class dump-directory lookup become DslGeneratedFileWriter.resolveClassDumpDir; OAL keeps its own, because its debug flag is settable independently of the environment variable and two tests rely on that. No behaviour change.
• Extend the GET /inspect/entities admin API to inspect a metric persisted by any OAP, even one this node does not define locally. When the metric is unknown to the local registry, the caller supplies valueColumn + valueType and the storage backend resolves the physical index/table/group from its own running config (no DB schema/table-metadata read): ES uses the merged metrics-all index + metric_table discriminator, JDBC probes the node's function tables by the table_name discriminator, and BanyanDB synthesizes a read-only measure schema. Scope is no longer required — the entity_id is decoded structurally (service / 2nd-level / relations) with a generic name leaf. Locally-defined metrics keep the exact field names, scope, and mqeEntity as before.
• Add the POST /inspect/values admin API — read the value series of a metric persisted by another OAP (one this node does not define locally) by supplying its {valueColumn, valueType}. The real MQE engine runs over a request-scoped InspectQueryContext overlay (provide-if-absent — the local catalog always wins) that makes the foreign metric look registered to every read path: ValueColumnMetadata resolves its value column / type / scope, and the storage location registries resolve where it lives (MetadataRegistry synthesizes a BanyanDB measure schema, IndexController resolves the ES metrics-all index, TableHelper probes the JDBC function tables), so the read returns the native MQE ExpressionResult with no per-DAO special-casing. Admin-only (a forced read this OAP cannot validate); not mirrored onto the public REST / GraphQL surface. See the Inspect API.
• Remove the always-on alarm-to-event conversion (EventHookCallback). A triggered alarm is no longer synthesized into the events pipeline as an Alarm/AlarmRecovery event; events now originate only from real event sources (agents, SkyWalking CLI, Kubernetes Event Exporter). Alarms remain available through the alarm store (getAlarm/queryAlarms) and the configured alarm hooks. This drops a documented "Known Event" and removes 1-2 synthetic event records per alarm fire.
• TLS for all OAP HTTP/REST servers, with cert hot-reload. Adds the restSSLEnabled / restSSLKeyPath / restSSLCertChainPath config structure to every OAP HTTP server — core REST, sharing-server, admin, PromQL, LogQL, TraceQL and Zipkin query/receiver — each with its own dedicated environment variables (SW_CORE_REST_SSL_*, SW_RECEIVER_SHARING_REST_SSL_*, SW_ADMIN_SERVER_REST_SSL_*, SW_PROMQL_REST_SSL_*, SW_LOGQL_REST_SSL_*, SW_TRACEQL_REST_SSL_*, SW_QUERY_ZIPKIN_REST_SSL_*, SW_RECEIVER_ZIPKIN_REST_SSL_*). The shared Armeria HTTPServer reloads the key pair from disk on rotation (via TlsProvider.ofScheduled) so refreshed cer

Download

https://skywalking.apache.org/downloads/

Notice

Don't download source codes from this page. Please follow build document, if you want to build source codes by yourself.

Project

• Introduce OAL V2 engine:
  • Immutable AST models for thread safety and predictable behavior
  • Type-safe enums replacing string-based filter operators
  • Precise error location reporting with file, line, and column numbers
  • Clean separation between parsing and code generation phases
  • Enhanced testability with models that can be constructed without parsing
• Introduce MAL/LAL/Hierarchy V2 engine — replace Groovy-based DSL runtime with ANTLR4 parser + Javassist bytecode generation:
  • Remove Groovy runtime dependency from OAP backend
  • Fail-fast compilation at startup — syntax and type errors are caught immediately instead of at first execution
  • Thread-safe generated classes with no ThreadLocal or shared mutable state
  • Immutable AST models for all three DSLs (MAL, LAL, Hierarchy rules)
  • Explicit context passing replaces Groovy binding/closure capture
  • v1 (Groovy) and v2 (ANTLR4+Javassist) cross-version checker validates behavioral equivalence across 1,290+ expressions
  • JMH benchmarks confirm v2 runtime speedups: MAL execute ~6.8x, LAL compile ~39x / execute ~2.8x, Hierarchy execute ~2.6x faster than Groovy v1
  • Generated class names follow {yamlFileName}_L{lineNo}_{ruleName} pattern for all DSLs (MAL/LAL/Hierarchy) for stack trace traceability
• Breaking Change — LAL: remove slowSql {} and sampledTrace {} sub-DSLs from the grammar. These are replaced by the configurable outputType mechanism:
  • Set outputType at the rule level in YAML config to specify the output entity class. Use the short name registered by LALOutputBuilder SPI (e.g., outputType: SlowSQL, outputType: SampledTrace), or a fully qualified class name as fallback.
  • LALOutputBuilder implementations are discovered via ServiceLoader and expose a name() method for short name resolution. Built-in types: SlowSQL (DatabaseSlowStatementBuilder), SampledTrace (SampledTraceBuilder).
  • Output fields (e.g., id, statement, latency) are now regular field assignments in the extractor block, no longer wrapped in sub-DSL blocks.
  • Custom output fields are validated against the output type's setters at compile time.
  • An explicit sink {} block is now required for data to be persisted. Without sink {}, no data is saved — this applies to all LAL rules including those using outputType. In v1, slowSql {} and sampledTrace {} dispatched data as a side-effect inside the extractor; in v2, persistence is always handled by the sink pipeline.
  • Output type resolution order: per-rule YAML outputType (short name via SPI or FQCN) > LALSourceTypeProvider SPI default > Log.class.
  • All bundled LAL scripts (mysql-slowsql.yaml, pgsql-slowsql.yaml, redis-slowsql.yaml, envoy-als.yaml, k8s-service.yaml, mesh-dp.yaml) have been updated.
  • Users with custom LAL scripts using slowSql {} or sampledTrace {} must migrate to the new syntax. See LAL documentation.
  • Rename ExtractorSpec to MetricExtractor — now only handles LAL metrics {} blocks. Standard field setters (service, layer, timestamp, etc.) are compiled as direct setter calls on the output builder.
  • Add def local variable support in LAL extractor (and filter level). Supports toJson() and toJsonArray() built-in functions for converting strings, Maps, and protobuf Struct to Gson JSON objects. Variables support null-safe navigation (?.), method chaining with compile-time type inference, and explicit type cast via as (built-in types or fully qualified class names, e.g., `def resp = parsed?.response as io.envoyproxy.envoy.data.acc

Download

https://skywalking.apache.org/downloads/

Notice

Don't download source codes from this page. Please follow build document, if you want to build source codes by yourself.

BanyanDB Storage Option is large-scale ready

BanyanDB is a native-built SkyWalking database that focuses entirely on SkyWalking use cases. BanyanDB demonstrates significant potential in improving performance and optimizing resource utilization. In typical deployment scenarios involving around 200 services and 200+ calls per second, a cluster configured with 2 liaison nodes and 2 data nodes—each equipped with 4 vCPUs and 8 GB memory—delivers stable and efficient performance. BanyanDB also supports full tracing sampling, providing trace collection capabilities up to 100%, ensuring comprehensive observability without compromising system stability.

New Trace Model in BanyanDB

Optimized the Trace model implementation for BanyanDB 0.9.0, significantly reducing query frequency between OAP and BanyanDB. Introduced new query views based on the latest query features, greatly reducing page latency.

Project

• Bump up BanyanDB dependency version(server and java-client) to 0.9.0.
• Fix CVE-2025-54057, restrict and validate url for widgets.
• Fix MetricsPersistentWorker, remove DataCarrier queue from Hour/Day dimensions metrics persistent process. This is important to reduce memory cost and Hour/Day dimensions metrics persistent latency.
• [Break Change] BanyanDB: support new Trace model.

OAP Server

• Implement self-monitoring for BanyanDB via OAP Server.
• BanyanDB: Support hot/warm/cold stages configuration.
• Fix query continues profiling policies error when the policy is already in the cache.
• Support hot/warm/cold stages TTL query in the status API and graphQL API.
• PromQL Service: traffic query support limit and regex match.
• Fix an edge case of HashCodeSelector(Integer#MIN_VALUE causes ArrayIndexOutOfBoundsException).
• Support Flink monitoring.
• BanyanDB: Support @ShardingKey for Measure tags.
• BanyanDB: Support cold stage data query for metrics/traces/logs.
• Increase the idle check interval of the message queue to 200ms to reduce CPU usage under low load conditions.
• Limit max attempts of DNS resolution of Istio ServiceEntry to 3, and do not wait for first resolution result in case the DNS is not resolvable at all.
• Support analysis waypoint metrics in Envoy ALS receiver.
• Add Ztunnel component in the topology.
• [Break Change] Change componentId to componentIds in the K8SServiceRelation Scope.
• Adapt the mesh metrics if detect the ambient mesh in the eBPF access log receiver.
• Add JSON format support for the /debugging/config/dump status API.
• Enhance status APIs to support multiple accept header values, e.g. Accept: application/json; charset=utf-8.
• Storage: separate SpanAttachedEventRecord for SkyWalking trace and Zipkin trace.
• [Break Change]BanyanDB: Setup new Group policy.
• Bump up commons-beanutils to 1.11.0.
• Refactor: simplify the Accept http header process.
• [Break Change]Storage: Move event from metrics to records.
• Remove string limitation in Jackson deserializer for ElasticSearch client.
• Fix disable.oal does not work.
• Enhance the stability of e2e PHP tests and update the PHP agent version.
• Add component ID for the dameng JDBC driver.
• BanyanDB: Support custom TopN pre-aggregation rules configuration in file bydb-topn.yml.
• refactor: implement OTEL handler with SPI for extensibility.
• chore: add toString implementa

Download

https://skywalking.apache.org/downloads/

Notice

Don't download source codes from this page. Please follow build document, if you want to build source codes by yourself.

No H2, More BanyanDB

• Add BanyanDB 0.8.0 support.
• H2 storage option is removed permanently.

Project

• Add doc_values for fields that need to be sorted or aggregated in Elasticsearch, and disable all others.
  • This change would not impact the existing deployment and its feature for our official release users.
  • Warning If there are custom query plugins for our Elasticsearch indices, this change could break them as sort queries and aggregation queries which used the unexpected fields are being blocked.
• [Breaking Change] Rename debugging-query module to status-query module. Relative exposed APIs are UNCHANGED.
• [Breaking Change] All jars of the skywalking-oap-server are no longer published through maven central. We will only publish the source tar and binary tar to the website download page, and docker images to docker hub.
  • Warning If you are using the skywalking-oap-server as a dependency in your project, you need to download the source tar from the website and publish them to your private maven repository.
• [Breaking Change] Remove H2 as storage option permanently. BanyanDB 0.8(OAP 10.2 required) is easy, stable and production-ready. Don't need H2 as default storage anymore.
• [Breaking Change] Bump up BanyanDB server version to 0.8.0. This version is not compatible with the previous versions. Please upgrade the BanyanDB server to 0.8.0 before upgrading OAP to 10.2.0.
• Bump up nodejs to v22.14.0 for the latest UI(booster-ui) compiling.
• Migrate tj-actions/changed-files to dorny/paths-filter.

OAP Server

• Skip processing OTLP metrics data points with flag FLAG_NO_RECORDED_VALUE, which causes exceptional result.
• Add self observability metrics for GraphQL query, graphql_query_latency.
• Reduce the count of process index and adding time range when query process index.
• Bump up Apache commons-io to 2.17.0.
• Polish eBPF so11y metrics and add error count for query metrics.
• Support query endpoint list with duration parameter(optional).
• Change the endpoint_traffic to updatable for the additional column last_ping.
• Add Component ID(5023) for the GoZero framework.
• Support Kong monitoring.
• Support adding additional attr[0-5] for service/endpoint level metrics.
• Support async-profiler feature for performance analysis.
• Add metrics value owner for metrics topN query result.
• Add naming control for EndpointDependencyBuilder.
• The index type BanyanDB.IndexRule.IndexType#TREE is removed. All indices are using IndexType#INVERTED now.
• Add max query size settings to BanyanDB.
• Fix "BanyanDBTraceQueryDAO.queryBasicTraces" doesn't support querying by "trace_id".
• Polish mesh data dispatcher: don't generate Instance/Endpoint metrics if they are empty.
• Adapt the new metadata standardization in Istio 1.24.
• Bump up netty to 4.1.115, grpc to 1.68.1, boringssl to 2.0.69.
• BanyanDB: Support update the Group settings when OAP starting.
• BanyanDB: Introduce index mode and refactor banyandb group settings.
• BanyanDB: Introduce the new Progressive TTL feature.
• BanyanDB: Support update the Schema when OAP starting.
• BanyanDB: Speed up OAP booting while initializing BanyanDB.
• BanyanDB: Support @EnableSort on the column to enable sorting for IndexRule and set the default to false.
• Support Get Effective TTL Configurations API.
• Fix ServerStatusService.statusWatchers concurrent modification.
• Add protection for dynamic config change propagate chain.
• Add Ruby component IDs(HttpClient=2, Redis=7, Memcached=20, Elasticsea