Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MongoDB Health System Notification #20410

Open
kimoswalt opened this issue Sep 10, 2024 · 1 comment
Open

MongoDB Health System Notification #20410

kimoswalt opened this issue Sep 10, 2024 · 1 comment

Comments

@kimoswalt
Copy link

kimoswalt commented Sep 10, 2024

What?

  • Can we get system notification or errors, in the UI, when MongoDB(single or multi-node) is down or in Recovering.
  • Similar to the OpenSearch cluster health notifications.
  • Or possibly something on the Node page.

Why?

  • Recently had a two case where customers Archiving was failing because one of their MongoDB nodes was in RECOVERING mode.

  • They had no idea that any of MongoDB nodes were having issues, and their archives were failing for several months.

  • If they had errors or notifications in the Graylog UI telling them their MongoDB nodes were unhealthy, or down, we may have been able to avoid the archiving issues.

Your Environment

  • Graylog Version: 6.0.5
  • MongoDB Version: 5.0.21
  • Operating System: Ubuntu

The environment I have the most detail on has
1 load balancer, 3 Graylog nodes, 3 OpenSearch nodes. The three Graylog nodes are also running MongoDB, and replication is configured.

@coffee-squirrel
Copy link

Just as a FYI for whoever-- to catch archival issues we (not one of the customers mentioned) have an event definition in place for message:"ARCHIVING_SUMMARY: Indices could not be archived yet" on the All system events stream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants