Pratik Mankawde f11ebc1253 fix: StatsDGauge dirty init + tx_submitter sequence drift in CI ...

Two CI failures traced to root cause:

1. rippled_jobq_job_count: 0 series — StatsDGaugeImpl declared
   m_dirty{false} despite the constructor comment saying "start dirty".
   Gauges whose value starts and stays at 0 never emitted, so Prometheus
   never scraped them.  Fix: m_dirty{true} on the member initializer.

2. TX error rate 82.8% — the submitter tracked account sequences
   locally, but in a multi-node consensus network other nodes' txns
   advance sequences independently.  After a few ledger closes the
   locally-tracked sequence fell behind the ledger, producing
   tefPAST_SEQ for every subsequent submission.  Fix: refresh account
   sequences from account_info every 10 s during the submission loop.

2026-04-24 19:42:20 +01:00

..

telemetry

fix: StatsDGauge dirty init + tx_submitter sequence drift in CI

2026-04-24 19:42:20 +01:00