-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New plugin to read RAID events #2841
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me the plugin looks good, I have added only minor comments.
What do you think about implementation, which will not require syslog in the chain? |
Hi! First of all, sorry for that prolonged silence. Thanks for taking a look at this. I'm going to post a patch that addresses your comments. Answering your question - from what I see, On the other hand, does having a syslog dependency is that painful? Thanks again and looking forward for your response! |
…from RAID arrays that were written to syslog by mdadm utility (which is a user-space software for managing the RAIDs). Then, based on configuration provided by user, plugin will decide whether to send the collectd notification or not. Mdevents needs the syslog and mdadm to be present on a platform that collectd is launched. Based on the naming of existing dpdk plugins (dpdkstat for metrics, dpdkevents for notifications) and the fact that there is already plugin called md for gathering metrics from RAIDs, giving this plugin name mdevents felt like the best option. A slight change to ignorelist API was introduced - it is now possible to retrieve the count of nodes in array and the current ignore setting for given array. ChangeLog: New plugin to read RAID events
This PR is something similar to or related to #3045 |
The longer chain - lower reliability. |
You are right @rpv-tomsk, functionally both plugins are watching files for particular messages to generate notification about. |
@mfijalko There is a failing test, would you mind having a look? |
Red Hat check have more verbose UT logs. |
At the moment collectd ci environment doesn't have dependency for removed unit test case.
Looks like all the changes requested has been resolved along with any of the UT/CI issues. Could we remove "changes requested"? |
@sunkuranganath At least I cannot. @rpv-tomsk Can you resolve the changerequest? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This plugin, named mdevents, is responsible for gathering the events from RAID arrays that were written to syslog by mdadm utility (which is a user-space software for managing the RAIDs). Then, based on configuration provided by user, plugin will decide whether to send the collectd notification or not.
Mdevents needs the syslog and mdadm to be present on a platform that collectd is launched.
Based on the naming of existing dpdk plugins (dpdkstat for metrics, dpdkevents for notifications) and the fact that there is already plugin called md for gathering metrics from RAIDs, giving this plugin name mdevents felt like the best option.
A slight change to ignorelist API was introduced - it is now possible to retrieve the count of nodes in array and the current ignore setting for given array.
ChangeLog: mdevents plugin: Generate notifications about events in RAID arrays.
[edit @kkepka:] added changelog