Google Git
Sign in
apache/skywalking/refs/heads/master
commit
5b481a41a99861249410118e4cfbf591c4508dae
[log]
author
吴晟 Wu Sheng <wu.sheng@foxmail.com>
Tue May 19 18:49:55 2026 +0800
committer
GitHub <noreply@github.com>
Tue May 19 18:49:55 2026 +0800
tree
82cb3aa4a88fe5b2c8040d37e5310024fc585c91
parent
137935d364be83d4b4438730540856cc35a2d5c8 [diff]
11.0.0: drop bundled UI, retire status public REST, add ui-management + queryAlarms (#13877)

* Remove the bundled legacy UI from the SkyWalking OAP distribution.
  * Drop the `apm-webapp` module, `skywalking-ui` submodule, UI Docker image build, `docker.ui` Maven target, webapp distribution packaging, and related startup scripts.
  * Remove boot-time dashboard/menu seeding and the legacy UI menu management storage/service model.
  * The official UI is now maintained separately as `apache/skywalking-horizon-ui`.

* Move dashboard template management from GraphQL to the admin server.
  * Remove `UIConfigurationManagement` GraphQL APIs and `SW_ENABLE_UPDATE_UI_TEMPLATE`.
  * Add the `ui-management` admin feature module with REST APIs for dashboard template list/get/create/update/disable operations.

* Restrict status and debugging REST APIs to the admin server.
  * `/status/*` and `/debugging/*` are now registered only on the admin server, default port `17128`.
  * Public REST binding is removed while keeping URI and payload formats unchanged.

* Add the new `queryAlarms(condition: AlarmQueryCondition!): Alarms` GraphQL API.
  * Supports filtering alarms by entities, layers, rule names, keyword, tags, duration, and paging.
  * Keeps the existing `getAlarm` API as deprecated compatibility surface.
  * Add `layer` to `AlarmRecord` and index `id0`/`id1` to support entity-based alarm filtering.
  * Add `IAlarmQueryDAO.queryAlarms(...)` and implement it for BanyanDB, Elasticsearch, and JDBC.

* Enable all admin feature modules by default.
  * `admin-server`, `status`, `inspect`, `ui-management`, `dsl-debugging`, and `receiver-runtime-rule` are enabled by default.
  * Operators can disable individual modules by setting the matching `SW_*` environment variable to empty.

* Update tests, E2E cases, release materials, and documentation for the new no-bundled-UI architecture.
  * E2E cases now access OAP directly instead of the removed UI proxy.
  * Status/debugging tests are updated to use the admin server port.
  * New alarm E2E cases cover `queryAlarms` filters.
407 files changed
tree: 82cb3aa4a88fe5b2c8040d37e5310024fc585c91
  1. .claude/
  2. .github/
  3. .mvn/
  4. apm-checkstyle/
  5. apm-dist/
  6. apm-protocol/
  7. benchmarks/
  8. changes/
  9. dist-material/
  10. docker/
  11. docs/
  12. oap-server/
  13. oap-server-bom/
  14. test/
  15. tools/
  16. .asf.yaml
  17. .dlc.json
  18. .gitignore
  19. .gitmodules
  20. .licenserc.yaml
  21. CLAUDE.md
  22. codeStyle.xml
  23. CONTRIBUTING.md
  24. HEADER
  25. LICENSE
  26. lombok.config
  27. Makefile
  28. mvnw
  29. mvnw.cmd
  30. NOTICE
  31. pom.xml
  32. README.md
README.md

Apache SkyWalking

SkyWalking: an APM (Application Performance Monitoring) system, especially designed for microservices, cloud native and container-based architectures.

GitHub stars X Follow

GitHub Release

Abstract

SkyWalking is an open-source APM system that provides monitoring, tracing and diagnosing capabilities for distributed systems in Cloud Native architectures.

  • Distributed Tracing
    • End-to-end distributed tracing. Service topology analysis, service-centric observability and APIs dashboards.
  • Agents for your stack
    • Java, .Net Core, PHP, NodeJS, Golang, LUA, Rust, C++, Client JavaScript and Python agents with active development and maintenance.
  • eBPF early adoption
    • Rover agent works as a monitor and profiler powered by eBPF to monitor Kubernetes deployments and diagnose CPU and network performance.
  • Scaling
    • 100+ billion telemetry data could be collected and analyzed from one SkyWalking cluster.
  • Mature Telemetry Ecosystems Supported
    • Metrics, Traces, and Logs from mature ecosystems are supported, e.g. Zipkin, OpenTelemetry, Prometheus, Zabbix, Fluentd
  • Native APM Database
    • BanyanDB, an observability database, created in 2022, aims to ingest, analyze and store telemetry/observability data.
  • Consistent Metrics Aggregation
    • SkyWalking native meter format and widely known metrics format(OpenTelemetry, Telegraf, Zabbix, e.g.) are processed through the same script pipeline.
  • Log Management Pipeline
    • Support log formatting, extract metrics, various sampling policies through script pipeline in high performance.
  • Alerting and Telemetry Pipelines
    • Support service-centric, deployment-centric, API-centric alarm rule setting. Support forwarding alarms and all telemetry data to 3rd party.
  • AI Power Enabled
    • Machine Learning (ML) and Artificial Intelligence (AI) analyze observability data to identify patterns and enhance capabilities, such as recognizing HTTP URI patterns and automatically calculating metric baselines for intelligent alerting, improving anomaly detection.

Live Demo

Documentation

Downloads

Please head to the releases page to download a release of Apache SkyWalking.

Compiling project

Follow this document.

Code of conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please follow the REPORTING GUIDELINES to report unacceptable behavior.

Contact Us

  • Mail list: dev@skywalking.apache.org. Mail to dev-subscribe@skywalking.apache.org, follow the reply to subscribe the mail list.
  • Send Request to join SkyWalking slack mail to the mail list(dev@skywalking.apache.org), we will invite you in.
  • For Chinese speaker, send [CN] Request to join SkyWalking slack mail to the mail list(dev@skywalking.apache.org), we will invite you in.
  • Twitter, ASFSkyWalking
  • bilibili B站 视频
  • 掘金

Our Users

Hundreds of companies and organizations use SkyWalking for research, production, and commercial purposes. Visit our website to find the user page.

License

Apache 2.0 License.