[banyandb]The --observability-modes=native parameter is not taking effect

[Hwting]

Hi,When testing banyandb with the configuration --observability-modes=native, the self-observability dashboard shows no data.

Deployment Method：

Expected outcome：
https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/cluster/#self-observability-dashboard

[wu-sheng]

I am not sure. @hanahmily, was this UI dropped in 0.11?

[hanahmily]

UI Plan: We have introduced Canopy (the new UI) in v0.11 alongside the original UI. In v0.12, we will completely remove the old UI.

Regarding the empty page: I’ll check if this is a server-side defect. If it is, I’ll fix it, cherry-pick the change into 0.11, and release a patch. However, if this is a UI-side issue, I plan to leave it as-is given the upcoming UI replacement.

[Hwting]

@hanahmily HI，May I ask a question? When I use docker-compose to deploy a cluster, I use File Mode: nodes.yaml.

Reference document ：https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/cluster/
The example port is 17912.：

Reference document ：https://skywalking.apache.org/docs/skywalking-banyandb/latest/operation/node-discovery/#file-based-discovery

The example port is 18912：

I also looked at it in combination with the liaison parameter：

When I used 17912 during deployment, it reported errors and anomalies; after changing to 18912, everything was normal.
I'm curious if this is a typo in the documentation? Should the correct port be 18912?”​

My nodes.yaml:
version: 0.11.0

nodes:
  - name: data-0
    grpc_address: 10.100.11.1:17912
  - name: data-1
    grpc_address: 10.100.11.2:17912
  - name: liaison-0
    grpc_address: 10.100.11.1:18912
  - name: liaison-1
    grpc_address: 10.100.11.2:18912

[hanahmily]

@Hwting Thanks for the report.

The default --grpc-port for both data and liaison is 17912. 18912 is only a common override when they share the same host/IP.

nodes.yaml must list the ports each process actually listens on. Same IP → different ports (e.g. data 17912, liaison 18912); separate IPs → both can use 17912. Your working setup matches the co-located case — we’ll align the docs.