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

Use correct ID for incident resolution #9321

merged 2 commits into from Oct 16, 2018


None yet
2 participants

laf commented Oct 12, 2018


Please note

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


If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926
After you are done testing, you can remove the changes with ./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.


This comment has been minimized.


murrant commented Oct 15, 2018

I thought this was supposed to be the id in the alert_log table so we we don't repeat ids for events.


This comment has been minimized.


laf commented Oct 15, 2018

It's supposed to be a static ID throughout the life of the alert otherwise PD can't match the recovery alert.

I've tested before and after this fix and with this on new transports it marks the alert as resolved. I haven't tested with the old transports but it should be the same.

@laf laf added this to the 1.44 milestone Oct 15, 2018

@murrant murrant merged commit 3fc9e33 into librenms:master Oct 16, 2018

3 checks passed

WIP ready for review
codeclimate All good!
license/cla Contributor License Agreement is signed.

@laf laf deleted the laf:community-5634 branch Oct 17, 2018

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