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: Use the correct high/high warn thresholds for junos dbm sensors #7056

Merged
merged 1 commit into from Jul 19, 2017

Conversation

Projects
None yet
5 participants
@laf
Copy link
Member

laf commented Jul 19, 2017

DO NOT DELETE THIS TEXT

Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926

Wrong OID's used here for the high sensors. Fixes: #7032

@mention-bot

This comment has been minimized.

Copy link

mention-bot commented Jul 19, 2017

Thank you for submitting a PR @laf! We have found the following @remydb based on the history of these files to review this PR.

@laf laf added the Bug 🐞 label Jul 19, 2017

@scrutinizer-notifier

This comment has been minimized.

Copy link

scrutinizer-notifier commented Jul 19, 2017

The inspection completed: No new issues

@murrant

This comment has been minimized.

Copy link
Member

murrant commented Jul 19, 2017

copypasta!

@murrant murrant merged commit c40825f into librenms:master Jul 19, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
license/cla Contributor License Agreement is signed.
Details

@laf laf deleted the laf:fix/issue-7032 branch Jul 19, 2017

@siegsters

This comment has been minimized.

Copy link
Contributor

siegsters commented Jul 19, 2017

Thanks for the quick fix! We installed this morning and no more alerts!

@lock

This comment has been minimized.

Copy link

lock bot commented May 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 17, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.