wu-sheng opened a new pull request, #271:
URL: https://github.com/apache/skywalking-showcase/pull/271

   ## What
   
   Adopts the **SWIP-15** cluster/node/group self-observability model for 
BanyanDB in the showcase (both Docker and Kubernetes modes), and refreshes the 
rendered `demo.yaml`.
   
   This depends on SWIP-15 having merged into OAP 
([apache/skywalking#13903](https://github.com/apache/skywalking/pull/13903)).
   
   ## Changes
   
   **Versions** (`Makefile.in`)
   - OAP → `c9f816a4de` — SWIP-15 redesigned BanyanDB so11y rules.
   - BanyanDB → `c2d925e4e` (#1169) — adds the queue batch/message metric 
families the new instance/endpoint rules read.
   
   **Docker single-node** (standalone, no FODC proxy)
   - `otel-collector-config-banyandb.yaml`: scrape `banyandb:2121` and inject 
the identity labels the new MAL rules key on — `cluster` / `container_name` / 
`node_role` / `node_type` / `pod_name` — replacing the obsolete `host_name: 
root[root]`. Mirrors the SWIP-15 e2e's no-FODC static-label pattern.
   - `docker-compose.single-node.yaml`: switch the OAP rule-enable from 
`banyandb` → `banyandb/*`. The rules now live in `otel-rules/banyandb/` (3 
files); bare `banyandb` matches no file and **fails OAP startup**.
   
   **Kubernetes** (BanyanDB cluster + FODC proxy — the documented production 
model)
   - `feature-banyandb-monitor/opentelemetry-config.yaml`: scrape the **FODC 
proxy** aggregated `/metrics` (`component=fodc-proxy`, port `http`) and inject 
only `cluster`; the proxy stamps the rest. Replaces the old per-pod 
`host_name`/`service_instance_id` model. Adds `scrape_interval: 10s` so the new 
`.rate('PT15S')` write/query/error metrics populate (default 60s is too coarse).
   - `values.yaml`: make `banyandb.cluster.fodc.enabled` explicit and expose 
the proxy http service as `ClusterIP` (chart default is `LoadBalancer`).
   
   **`demo.yaml`** — regenerated. Now renders banyandb-helm **0.6.0** with the 
FODC proxy and the new images; the previous snapshot was the pre-FODC 
`0.5.0-rc0` / etcd chart (a year stale), so the diff is large.
   
   ## Verification
   
   Deployed the full stack to a local **kind** cluster (BanyanDB cluster 
hot/warm/cold + liaison + FODC proxy/agents + OAP + otel-collector) and 
confirmed end-to-end:
   
   - FODC proxy `/metrics` emits 
`container_name`/`node_role`/`node_type`/`pod_name` across all nodes.
   - otel collector scrapes the proxy and injects `cluster: showcase-banyandb`.
   - OAP loads the SWIP-15 banyandb rules (service/instance/endpoint).
   - `listServices(layer:"BANYANDB")` → `showcase-banyandb`; instances resolve 
as `pod@container` with role/type; endpoints resolve as storage groups 
(`sw_metricsMinute`, `sw_metadata`, …).
   - Gauge metrics (`total_cpu_cores`, `total_memory_used`, 
`reporting_instances`) and rate metrics (`cluster_write_rate`, 
`cluster_query_rate`) all populate; `cluster_error_rate` 0 (healthy).
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to