Hello list.

I'm trying to keep track of cfengine execution time, in order to monitor 
policy changes effect.

The easiest way seems to add start/stop messages in the logs.

If invocating cfagent from a cron task, it's quite simple, but doesn't 
allow to discriminate between update and main phase:
1 * * * * logger "cfengine start"; cfagent; logger "cfengine stop"

If using cfexecd as a daemon, the following should work, and be usable 
both for update and for main phase:

actionsequence = (
     shellcommands.seq_start
     ....
     shellcommands.seq_stop
)

shellcommands:
     seq_start::
         logger "cfengine start"

     seq_stop
        logger "cfengine stop"

Then a monitoring agent plugin could get timestamps from the logs, and 
compute execution time.

But maybe they are better/easier ways to do it ? cfengine has a lot of 
files under its state directory, but none seems to have the relevant 
informations.
-- 
Guillaume Rousse
Service des Moyens Informatiques
INRIA Saclay - Île-de-France
Parc Orsay Université, 4 rue J. Monod
91893 Orsay Cedex France
Tel: 01 69 35 69 62
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to