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

Added ironware syslog notify code #8268

Merged
merged 2 commits into from Feb 21, 2018

Conversation

Projects
None yet
4 participants
@lewisvive
Contributor

lewisvive commented Feb 20, 2018

Updated syslog notify code to allow Brocade devices to fire oxidized update.

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

@CLAassistant

This comment has been minimized.

CLAassistant commented Feb 20, 2018

CLA assistant check
All committers have signed the CLA.

@scrutinizer-notifier

This comment has been minimized.

scrutinizer-notifier commented Feb 21, 2018

The inspection completed: No new issues

@laf laf merged commit 0e0c8d1 into librenms:master Feb 21, 2018

2 checks passed

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

This comment has been minimized.

Member

laf commented Feb 21, 2018

Thanks very much @lewisvive :)

wiad pushed a commit to wiad/librenms that referenced this pull request Feb 23, 2018

feature: Added ironware syslog notify code (librenms#8268)
* Added ironware syslog notify code

* Update syslog-notify-oxidized.php

inetAnt added a commit to criteo-forks/librenms that referenced this pull request Mar 19, 2018

feature: Added ironware syslog notify code (librenms#8268)
* Added ironware syslog notify code

* Update syslog-notify-oxidized.php
@lock

This comment has been minimized.

lock bot commented May 16, 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 16, 2018

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