You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wa...@apache.org on 2026/08/26 07:38:59 UTC
(skywalking-showcase) 01/01: UI support login audit logs
This is an automated email from the ASF dual-hosted git repository.
wankai123 pushed a commit to branch login-audit-log
in repository https://gitbox.apache.org/repos/asf/skywalking-showcase.git
commit 7b0c1fb36a24b9aa44100ee099cb4b85d2d34d1d
Author: wankai123 <wa...@foxmail.com>
AuthorDate: Wed Aug 26 15:38:40 2026 +0800
UI support login audit logs
---
Makefile.in | 7 +++----
deploy/platform/kubernetes/Makefile | 14 ++++++++++++++
deploy/platform/kubernetes/values.yaml | 14 +++++++++++++-
3 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/Makefile.in b/Makefile.in
index 44eb839..452a0a4 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -30,7 +30,7 @@ BANYANDB_IMAGE ?= ghcr.io/apache/skywalking-banyandb
# must exist AND the carrier must ship the first-party samplers (sw-trace-sampler.so,
# zipkin-trace-sampler.so), which land in d552528a — an earlier tag carries only the reference
# latencystatussampler.so, and the sampler then fails to load with "realpath failed".
-BANYANDB_IMAGE_TAG ?= da86fc478244674b89e409d5bac70ef242fe78e8
+BANYANDB_IMAGE_TAG ?= ba66af947c99c5a41ddf5009c92be00e5d308a11
STORAGE_CLASS ?= ""
ES_IMAGE ?= docker.elastic.co/elasticsearch/elasticsearch-oss
@@ -38,11 +38,10 @@ ES_IMAGE_TAG ?= 7.10.2
SW_OAP_IMAGE ?= ghcr.io/apache/skywalking/oap
# banyandb-tail-sampling needs the bydb.yml `pipeline` block, which lands in c66a476a (#13965).
-SW_OAP_IMAGE_TAG ?= 521b2ab5d665d91fb9771258cbb95db33aa6cd16
+SW_OAP_IMAGE_TAG ?= 7903c44dacdab1dcbf7acf9c11bea75547bca594
SW_UI_IMAGE ?= ghcr.io/apache/skywalking-horizon-ui
-# v0.7.0 - Browser logs tab and source-map de-obfuscation
-SW_UI_IMAGE_TAG ?= 66ddf68beea927989d64f75adf0f51be83958596
+SW_UI_IMAGE_TAG ?= ef3a161539d983bcabf25261ea2125562a7ecbe8
SW_CLI_IMAGE ?= ghcr.io/apache/skywalking-cli/skywalking-cli:bce7faaabbd57ed1f40156af8a8eb6c3eccea4ae
SW_EVENT_EXPORTER_IMAGE ?= ghcr.io/apache/skywalking-kubernetes-event-exporter/skywalking-kubernetes-event-exporter:8a012a3f968cb139f817189afb9b3748841bba22
diff --git a/deploy/platform/kubernetes/Makefile b/deploy/platform/kubernetes/Makefile
index ce7184d..2ebe881 100644
--- a/deploy/platform/kubernetes/Makefile
+++ b/deploy/platform/kubernetes/Makefile
@@ -98,11 +98,25 @@ feature-postgresql:
$(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.oap.storageType=postgresql)
$(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.postgresql.enabled=true)
+# Horizon's login audit rides along with this feature, in the very BanyanDB the stack already
+# runs for OAP: it keeps its records in groups of its own (horizon_audit, horizon_audit_metrics),
+# so nothing it writes can collide with OAP's data. Wired here rather than in values.yaml because
+# the liaison service name is derived from $(RELEASE), and because there is no BanyanDB to write
+# to under the elasticsearch / postgresql storage features.
+# allowCleartext: the liaison is reached over the cluster network with no TLS, and a
+# non-loopback address without it is refused at boot (the records carry usernames and
+# source addresses). Fine for the showcase; not for anything reachable by anyone else.
+# retentionDays: 7, in the spirit of the short TTLs the demo gives OAP's own groups.
.PHONY: feature-banyandb
feature-banyandb:
$(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.oap.storageType=banyandb)
$(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.banyandb.enabled=true)
$(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.banyandb.canopy.enabled=true)
+ $(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.ui.config.audit.enabled=true)
+ $(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.ui.config.audit.provider=banyandb)
+ $(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.ui.config.audit.banyandb.address=$(RELEASE)-banyandb-grpc:17912)
+ $(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.ui.config.audit.banyandb.allowCleartext=true)
+ $(eval HELM_OPTIONS := $(HELM_OPTIONS) --set skywalking.ui.config.audit.banyandb.retentionDays=7)
.PHONY: feature-so11y
feature-so11y:
diff --git a/deploy/platform/kubernetes/values.yaml b/deploy/platform/kubernetes/values.yaml
index c0d20e8..a0eda7c 100644
--- a/deploy/platform/kubernetes/values.yaml
+++ b/deploy/platform/kubernetes/values.yaml
@@ -94,7 +94,7 @@ skywalking:
SW_STORAGE_BANYANDB_METRICS_DAY_WARM_TTL_DAYS: "7"
SW_STORAGE_BANYANDB_METRICS_DAY_COLD_TTL_DAYS: "30"
SW_STORAGE_BANYANDB_METADATA_TTL_DAYS: "60"
- SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS: "0.9,0.10"
+ SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS: "0.10,0.11"
# Trace tail sampling: enabling a group's pipeline is what activates the sampler, since OAP
# pushes it onto that group as a TracePipelineConfig and the data node loads the matching
# .so (sw-trace-sampler.so / zipkin-trace-sampler.so). Everything else — the events, the
@@ -289,6 +289,18 @@ skywalking:
# # Workspace tenant without a claim naming which.
# roleByDomain:
# example.com: [maintainer]
+ # Login audit — a durable record of who signed in, on the Admin → Login audit
+ # page. NOT set here: the `banyandb` storage feature wires it (see the Makefile),
+ # because the liaison address it writes to is derived from $(RELEASE), and the
+ # elasticsearch / postgresql features deploy no BanyanDB for it to write to.
+ # It lands in this same block as:
+ # audit:
+ # enabled: true
+ # provider: banyandb
+ # banyandb:
+ # address: <release>-banyandb-grpc:17912
+ # allowCleartext: true
+ # retentionDays: 7
banyandb:
enabled: false
image: