Skip to content
This repository was archived by the owner on Sep 17, 2021. It is now read-only.

Conversation

@DenverJ
Copy link
Contributor

@DenverJ DenverJ commented Aug 13, 2015

This addresses some of the points in #157 - namely watchers and auditors as pluggable modules which allows people to drop in their own modules and have multiple auditors related to one watcher/technology. It all reduces the amount of boilerplate code required to set up a new 'monitor'.

This finds all watchers and auditors under the relevant paths and ignores any modules in the respective 'custom' folders.

The watchers and auditors use meta-classes to register themselves as valid watchers/auditors.

@scriptsrc scriptsrc self-assigned this Aug 17, 2015
@scriptsrc
Copy link
Contributor

This looks promising. It's taking some time to review because it's a larger change. I want to make sure @DenverJ knows this PR is appreciated.

@cstewart87
Copy link

Any plans to incorporate these changes any time soon? Also, is there any accompanying documentation for how to implement new watchers/auditors using this pluggable framework?

(BTW - 👍 for these changes!)

@huntergregal
Copy link

This would be a huge improvement. I would very much like to see this incorporated into the master branch. It would streamline development and make it easier for people to contribute.

So... bump 💯 :)

@aebie
Copy link

aebie commented Mar 21, 2016

Is there any timeline for merging this? I have been working on something similar but would very much prefer to pull down from master.

@scriptsrc
Copy link
Contributor

Hey @DenverJ - Thanks a bunch for this PR. We ended up merging it in with PR #405 & #410.

It took a while, but I'm super happy with it.

@scriptsrc scriptsrc closed this Sep 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants