Skip to content

Monitor hashed connectors - #2888

Open
delthas wants to merge 1 commit into
improvement/BB-906/hashed-oplog-ingestionfrom
improvement/BB-906/hashed-oplog-monitoring
Open

delthas wants to merge 1 commit into
improvement/BB-906/hashed-oplog-ingestionfrom
improvement/BB-906/hashed-oplog-monitoring

Conversation

@delthas

@delthas delthas commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Alerts on paused or hand-edited hashed connectors, and on migrations not completing. The dashboard overview gathers what applies to both ingestion modes (hashed ingestion now also fills the pipeline size, bandwidth and reconfiguration panels), followed by a hashed ingestion row; the panels that stay empty with hashed ingestion move to a collapsed row.

Part of the hashed oplog ingestion stack, overview in #2869.

Dashboard:
9

Issue: BB-906

@delthas
delthas added this pull request to stack #2886 October 15, 2026 15:35
@codecov

codecov Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.44%. Comparing base (c71bec8) to head (5c2bfe2).

Additional details and impacted files

Impacted file tree graph
see 7 files with indirect coverage changes

Components Coverage Δ
Bucket Notification 80.25% <ø> (ø)
Core Library 83.76% <ø> (+0.06%) ⬆️
Ingestion 79.17% <ø> (ø)
Lifecycle 81.70% <ø> (ø)
Oplog Populator 89.80% <ø> (ø)
Replication 64.47% <ø> (ø)
Bucket Scanner 85.76% <ø> (ø)
@@                              Coverage Diff                              @@
##           improvement/BB-906/hashed-oplog-ingestion    #2888      +/-   ##
=============================================================================
+ Coverage                                      77.41%   77.44%   +0.02%     
=============================================================================
  Files                                            214      214              
  Lines                                          14681    14681              
=============================================================================
+ Hits                                           11366    11370       +4     
+ Misses                                          3305     3301       -4     
  Partials                                          10       10              
Flag Coverage Δ
api:retry 9.02% <ø> (ø)
api:routes 8.87% <ø> (ø)
bucket-scanner 85.76% <ø> (ø)
ft_test:queuepopulator 9.51% <ø> (-0.97%) ⬇️
ingestion 12.53% <ø> (ø)
lib 8.80% <ø> (ø)
lifecycle 20.24% <ø> (-0.01%) ⬇️
notification 0.96% <ø> (ø)
oplogPopulator 0.16% <ø> (ø)
replication 18.54% <ø> (+0.09%) ⬆️
unit 59.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@delthas
delthas force-pushed the improvement/BB-906/hashed-oplog-monitoring branch from e2f7ca6 to bc5188c Compare October 15, 2026 17:40
@delthas
delthas force-pushed the improvement/BB-906/hashed-oplog-monitoring branch from bc5188c to 50b7ff7 Compare October 15, 2026 17:56
Alerts on paused or hand-edited hashed connectors, and on migrations
not completing.

The dashboard overview gathers what applies to both ingestion modes,
including the per-connector oplog lag reported by the mongo-kafka
connector, followed by a hashed ingestion row. The panels that stay
empty with hashed ingestion (bucket counts and changes, acknowledgement
lag) move to a collapsed row.

dashboard.json is generated with grafanalib 0.6.3, as the rest of the
file was.

Issue: BB-906
@delthas
delthas force-pushed the improvement/BB-906/hashed-oplog-monitoring branch from 50b7ff7 to 5c2bfe2 Compare October 15, 2026 18:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant