fix(gecko): replace dead WBNB/BUSD pool with active USDT/WBNB V3 on BNB#920
Merged
Conversation
Symptom: alertmanager fires 'geckoterminal head_lag stale on bnb' every few hours across all 3 regions in both staging and prod (observed 2026-07-06). Root cause: the BNB pool configured across 3 harnesses uses PoolID '24' which points to WBNB/BUSD PancakeSwap V2 — near-idle since Binance stopped issuing BUSD in 2024. Staging-sgp logs show 2 gecko/bnb samples per 5000 log lines vs 7 for base and 1 for solana; the sub-5min sample cadence the head_lag rule expects is impossible on a dead pool. Fix: replace with PancakeSwap V3 USDT/WBNB 0.01% fee tier, currently the #1 BSC pool by volume ($130M+ 24h). Internal GT pool_id = 160787671 (derived from app.geckoterminal.com/api/p1/bsc/pools/0x172fcd41e0913e95784454622d1c3724f546f849). Applied to all 3 harnesses that hardcode the same list: - aggregator-head-lag (fires the alert) - aggregator-latency-benchmark - metadata-coverage
Flotapponnier
added a commit
that referenced
this pull request
Jul 6, 2026
… (#921) Symptom: alertmanager fires 'geckoterminal head_lag stale on bnb' every few hours across all 3 regions in both staging and prod (observed 2026-07-06). Root cause: the BNB pool configured across 3 harnesses uses PoolID '24' which points to WBNB/BUSD PancakeSwap V2 — near-idle since Binance stopped issuing BUSD in 2024. Staging-sgp logs show 2 gecko/bnb samples per 5000 log lines vs 7 for base and 1 for solana; the sub-5min sample cadence the head_lag rule expects is impossible on a dead pool. Fix: replace with PancakeSwap V3 USDT/WBNB 0.01% fee tier, currently the #1 BSC pool by volume ($130M+ 24h). Internal GT pool_id = 160787671 (derived from app.geckoterminal.com/api/p1/bsc/pools/0x172fcd41e0913e95784454622d1c3724f546f849). Applied to all 3 harnesses that hardcode the same list: - aggregator-head-lag (fires the alert) - aggregator-latency-benchmark - metadata-coverage Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
added a commit
that referenced
this pull request
Jul 6, 2026
Rename AggregatorHeadLagStale to MobulaHeadLagStale and filter the expression on aggregator='mobula'. Non-Mobula aggregator health (gecko, codex, ...) is tracked via log tailing, not paged. Operator feedback 2026-07-06: 'on veut dans l'alerting seulement si ca concerne mobula; le reste on sen fou'. The rule previously fired every few hours on gecko/bnb because the WBNB/BUSD pool went idle in 2024 (separate fix #920 replaces that pool with WBNB/USDT V3), and periodically on codex due to WS disconnects — both being third-party issues Mobula operators cannot act on. Prometheus alert_type label + severity stay identical so the alertmanager routing / silencer rules keep working. Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
added a commit
that referenced
this pull request
Jul 6, 2026
Rename AggregatorHeadLagStale to MobulaHeadLagStale and filter the expression on aggregator='mobula'. Non-Mobula aggregator health (gecko, codex, ...) is tracked via log tailing, not paged. Operator feedback 2026-07-06: 'on veut dans l'alerting seulement si ca concerne mobula; le reste on sen fou'. The rule previously fired every few hours on gecko/bnb because the WBNB/BUSD pool went idle in 2024 (separate fix #920 replaces that pool with WBNB/USDT V3), and periodically on codex due to WS disconnects — both being third-party issues Mobula operators cannot act on. Prometheus alert_type label + severity stay identical so the alertmanager routing / silencer rules keep working. Co-authored-by: Florent Tapponnier <contact@mobula.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Symptom
Alertmanager fires
geckoterminal head_lag stale on bnbevery few hours across all 3 regions in staging and prod:Root cause
The BNB pool configured across 3 harnesses uses
PoolID: "24"which points to WBNB/BUSD PancakeSwap V2 — near-idle since Binance stopped issuing new BUSD in September 2024.Staging-sgp log evidence (last 5000 lines):
gecko/bnb: 2 samplesgecko/base: 7 samplesgecko/solana: 1 sampleThe 5-min sample-freshness rule in
alert_rules.ymlfires because the pool physically has fewer than 1 swap per 5 min.Fix
Replace with PancakeSwap V3 USDT/WBNB 0.01% — currently the #1 BSC pool by 24h volume ($130M+).
0x172fcd41e0913e95784454622d1c3724f546f849160787671(viaapp.geckoterminal.com/api/p1/bsc/pools/<address>)Scope
Same fix applied to all 3 harnesses that hardcode the same pool list:
aggregator-head-lag(the one firing the alert)aggregator-latency-benchmarkmetadata-coverageTest plan
go vetclean on the affected files[HEAD-LAG][GECKO][*][bnb]samples arriving every 30-120 s instead of every 15-30 mingecko_head_lag_stale{chain="bnb"}