I configure monitoring by letting puppet create exported resources on all hosts (where my rules then figure out what to monitor).. and then I simply pull those resources on the monitor servers - which results in config files for the things to monitor. Works beautifully with nagios/icinga and other text-based configs.
if I were to interface with something stupid (like stuff needing guy/rest-api to update config).. I'd still make puppet write config files.. perhaps in json format - and then simply catch puppet return code in script running puppet on the "config server that pulls the exported resources".. and post those new json files (filestamp tells it like it is ;) - to the config endpoint. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/24d44f87-f960-414d-89f4-cdaef2dd52d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
