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

Fix mongodb_up not set when instance is down #624

Closed
wants to merge 1 commit into from

Conversation

Sancretor
Copy link

When a MongoDB instance is down, the exporter does not produce any metrics, while we would expect it to return mongodb_up 0. This fix is an attempt to fix issues described in #347, #444 and #483.

It's my first PR on Go code so any feedback would be useful !

Also, sorry if I missed something on the whole PR process, don't hesitate to tell me 😅


  • Tests passed.
  • Fix conflicts with target branch.
  • Update jira ticket description if needed.
  • Attach screenshots/console output to confirm new behavior to jira ticket, if applicable.

Once all checks pass and the code is ready for review, please add pmm-review-exporters team as the reviewer. That would assign people from the review team automatically. Report any issues on our Forum or Discord.

@Sancretor Sancretor requested a review from a team as a code owner February 14, 2023 10:53
@Sancretor Sancretor requested review from tshcherban and JiriCtvrtka and removed request for a team February 14, 2023 10:53
@nevarsin
Copy link

Hi, what are the time expectations of approval? without this feature the exporter is currently unfit for reliability monitoring

@hemantlinux
Copy link

I am also facing same issue. Let me know if it fixed.

@JiriCtvrtka JiriCtvrtka requested review from ademidoff and BupycHuk and removed request for tshcherban and ritbl December 7, 2023 09:09
@JiriCtvrtka
Copy link
Contributor

@Sancretor Could you resolve conflicts? PR looks good and then we can proceed to merging of it. Thank you.

@BupycHuk
Copy link
Member

BupycHuk commented Dec 7, 2023

Hi @Sancretor, sorry for bothering you. We found out that similar changes were merged as part of #653 and we already released it in v0.40.0 . Thank you for the contribution, we are closing this PR as duplication.

@BupycHuk BupycHuk closed this Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants