Caideyipi opened a new pull request, #18517:
URL: https://github.com/apache/iotdb/pull/18517

   ## Description
   
   Add a standalone Grafana dashboard and Prometheus alert-rule example for 
IoTConsensus-based subscriptions.
   
   The dashboard:
   
   - filters by cluster, DataNode instance, consumer-group/topic queue, and 
DataRegion;
   - shows queue replicas, preferred-writer activity, initialization, 
approximate lag, uncommitted events, and response-byte transfer;
   - surfaces WAL-gap, routing-epoch, watermark, and seek/reset diagnostics;
   - documents the metric semantics and provides operational validation steps.
   
   The alert examples cover skipped WAL indexes, missing active 
preferred-writer queues, dormant queues with pending work, and pending work 
with no response-byte delivery.
   
   The dashboard intentionally does not claim an exact remaining event count, 
ETA, or authoritative commit-stall status. `subscription_consensus_lag` is an 
approximate queue-local work indicator, and the current metrics do not expose a 
precise backlog or a progress CLI. The `NoDelivery` alert is therefore a 
consumer-delivery diagnostic, not proof of stalled ACK/commit progress. The 
legacy `mode=consensus` value is documented as normalized to `mode=incremental`.
   
   This PR targets `apache/iotdb:master`; it is not based on 2.0.11.1 or a 
Timecho branch.
   
   ## Verification
   
   - Parsed `consensus-subscription-dashboard.json` with PowerShell 
`ConvertFrom-Json`.
   - Parsed `consensus-subscription-alert-rules.yml` with SnakeYAML 2.6.
   - Checked dashboard panel-ID uniqueness and datasource placeholders.
   - Checked that dashboard and alert PromQL expressions use 
`nodeType=DATANODE`.
   - Checked all referenced subscription metric names against the latest 
`origin/master` metric definitions.
   - Ran `git diff --cached --check`.
   - `promtool` was not installed in the local environment, so `promtool check 
rules` could not be run.
   
   No Java source or runtime behavior is changed by this PR.


-- 
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