[lsc-changes] [Ldap Synchronization...] page changed: documentation:2.0:monitoring:start

[webmaster]

A page in your DokuWiki was added or changed. Here are the details:

Date : 2012/07/20 10:10
Browser : Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1
IP-Address : 88.173.78.196
Hostname : mne69-10-88-173-78-196.fbx.proxad.net
Old Revision: http://lsc-project.org/wiki/documentation/2.0/monitoring/start?rev=1342771615
New Revision: http://lsc-project.org/wiki/documentation/2.0/monitoring/start
Edit Summary:
User : coudot

@@ -3,9 +3,9 @@
LSC provides script to check status in Nagios.

===== Check LSC status file =====

- This script parses LSC logfile to find a status line, and extract the folowing data:
+ This script parses LSC logfile to find a status line, and extract the following data:
* Total of entries
* Entries do modify
* Modified entries
* Entries in error
@@ -27,17 +27,39 @@
</file>

This file is erased at each launch, so you are sure to get the latest status.

- You can then use the monitoring script :
+ You can then use the monitoring script:
<code>
./check_lsc_status_file.pl -w 1 -c 1 -l /tmp/lsc/log/lsc.status -f -d 3600
</code>

The options are:
- * ''w'': Warning level
+ * ''w'': Wwrning level
* ''c'': critical level
* ''l'': log file
* ''d'': log file max age in seconds
* ''f'': perfparse data

+ ===== Check LSC remote =====

+ When LSC is launched as an asynchronous task, you cannot get the status trough log file.
+
+ Instead, you can use LSC agent script to get the status. A Nagios script doing this is provided and extract the following data:
+ * Total of entries
+ * Entries do modify
+ * Modified entries
+ * Entries in error
+
+ You can use the monitoring script like this:
+ <code>
+ ./check_lsc_remote.pl -H localhost -p 1099 -w 1 -c 1 -t user -f
+ </code>
+
+ The options are:
+ * ''w'': warning level
+ * ''c'': critical level
+ * ''H'': JMX host
+ * ''p'': JMX port
+ * ''f'': perfparse data
+ * ''t'': task name
+ * ''b'': path to lsc-agent script