[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2 2014-05-09T07:36:53Z 2014-05-09T07:36:53Z wiz wiz@pkgsrc.org 2014-05-09T07:36:53Z urn:sha1:6110b3907a630ba5f56311a5b07f346b35648583 until proven otherwise. 2014-01-25T10:29:56Z wiz wiz@pkgsrc.org 2014-01-25T10:29:56Z urn:sha1:4fc0b0ed6a186ccd83fc93c34cc9ed91862930d8 either because they themselves are not ready or because a dependency isn't. This is annotated by PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z or PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar respectively, please use the same style for other packages, and check during updates. Use versioned_dependencies.mk where applicable. Use REPLACE_PYTHON instead of handcoded alternatives, where applicable. Reorder Makefile sections into standard order, where applicable. Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default with the next commit. Whitespace cleanups and other nits corrected, where necessary. 2013-04-22T09:39:21Z imil imil@pkgsrc.org 2013-04-22T09:39:21Z urn:sha1:8129a42716654ded4b036f41487d04776f3d9c26 Collection. Monitoring is an API with a DSL feel to write monitoring daemons in Python. Monitoring works well for the following tasks: * to be notified when incidents happen (email, XMPP, ZeroMQ...) * automatic actions to be taken (restart, rm, git pull...) * to collect system statistics for further processing e.g. graphs * tie into existing/third-party Python code * play along nicely with existing deployment/configuration ecosystem (fabric/cuisine) Overview * monitoring DSL: declarative programming to define monitoring strategy * wide spectrum: from data collection and incident reporting to taking automatic actions * Small, easy to read, a single file API * Revised BSD License Use Cases * ensure service availability: test and start/stop when problems * collect system statistics/data, log locally and/or remotely * alert on system/service health, take actions