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

add bi aggregation function of min OK and exact OK #550

Conversation

elwood218
Copy link

Thank you for your interest in contributing to Checkmk!
Unfortunately, due to our current work load, we only consider pure bug fixes as stated in our Readme.
This means any new pull request that is not a pure bug fix will be closed.
Instead of creating a PR, please consider sharing new check plugins, agent plugins, special agents or notification plugins via the Checkmk Exchange.

General information

At the moment the aggregation function of BI only got count of OK nodes bigger or same as (>=). But having a count of exact OK nodes would have the option to check if there is only one Master node in an HA-Setup or more.

Bug reports

...

Proposed changes

The change here will add another option of exact OK nodes. So if I put it to 1 then only 1 OK nodes are ok and not 2.
Therefore the recent "CountOK" was set to == and add another function was added called MinOK which is calculating the OK as it was before ">=".
I have tested it and it worked. But the translation of the new options still needs to be added.

@elwood218
Copy link
Author

@kain88-de Where the new translations can be added or will you do that? What else is needed here? Only rebase?

@TimotheusBachinger
Copy link
Contributor

Dear Checkmk Contributor! Unfortunately, we had to re-write our git-repo history, rendering your PR auto-closed. We will therefore rebase your PR onto the current master and reopen it again. Sorry for the inconvenience.

@TimotheusBachinger
Copy link
Contributor

Dear Contributor. Unfortunately, we learned that re-opening a PR which was force-rebased, is not possible (see isaacs/github#361). Therefore we kindly ask you to create a new PR for your change. We apologize for the circumstances and will implement technical measures to prevent such incidents in the future.

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.

5 participants