Monitoring¶
Functions¶
register_file_monitor¶
-
File or a directory to watch for its modification.
-
Existing signal to raise or Signal Target to register signal implicitly.
Available signal targets:
1 2 3 4 5 6 7 8 9 10 11
* ``workers`` - run the signal handler on all the workers * ``workerN`` - run the signal handler only on worker N * ``worker``/``worker0`` - run the signal handler on the first available worker * ``active-workers`` - run the signal handlers on all the active [non-cheaped] workers * ``mules`` - run the signal handler on all mules * ``muleN`` - run the signal handler on mule N * ``mule``/``mule0`` - run the signal handler on the first available mule * ``spooler`` - run the signal on the first available spooler * ``farmN/farm_XXX`` - run the signal handler in the mule farm N or named XXX -
TaskChecker to be used for task execution requirements checking.
Maps a specific file/directory modification event to a signal.
ValueError If unable to register monitor.
Classes¶
Metric¶
User metric related stuff.
Note
One needs to register user metric beforehand.
E.g.:: section.monitoring.register_metric(section.monitoring.metric_types.absolute('mymetric'))
decr¶
Decrements the specified metric key value by the specified value.
incr¶
Increments the specified metric key value by the specified value.
mul¶
Multiplies the specified metric key value by the specified value.