On 04/27/2016 12:12 PM, Kristoffer Grönlund wrote: > Ken Gaillot <kgail...@redhat.com> writes: > >> The most prominent feature will be Klaus Wenninger's new implementation >> of event-driven alerts -- the ability to call scripts whenever >> interesting events occur (nodes joining/leaving, resources >> starting/stopping, etc.). >> >> This is the improved successor to both the ClusterMon resource agent and >> the experimental "notification-agent" feature that has been in the >> upstream master branch. >> >> The new feature was renamed to "alerts" to avoid confusion with the >> unrelated "notify" resource action. >> >> High-level tools such as crm and pcs should eventually provide an easy >> way to configure this, but at the XML level, the cluster configuration >> may now contain an alerts section: > There is now a branch with experimental early support for configuring > alerts in crmsh: > > https://github.com/ClusterLabs/crmsh/pull/136 > > Proposed syntax right now looks like this: > > alert <id> <path> \ > [attribute <nvpair> ...] \ > [meta <nvpair> ...] \ > [to <recipient \ > [attribute <nvpair> ...] \ > [meta <nvpair> ...] ...] > > Example: > > alert alert-1 /srv/pacemaker/pcmk_alert_sample.sh \ > to /var/log/cluster-alerts.log Are (and if yes how) you planning to handle multiple recipients? > > Opinions / suggestions are more than welcome! > > I'll hold off merging this until the feature stabilises in the pacemaker > repository. Although support by high-level tooling increases the amount of feedback which in turn should speed up the stabilization process ;-) > > Cheers, > Kristoffer >
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
