Agentcmd Logging Info Interferes With Custom Monitor Output|
In 7.2 the agentcmd has extra logging enabled that often interferes with the regular output from a custom monitor. It is possible to omit this extra logging output with the following steps. If you find your custom monitor behaves differently after upgrading to up.time 7.2, you can verify if the agentcmd logging output is the culprit by running the following command. <uptime_dir>/scripts/agentcmd -s -p 9998 localhost ver If the output returned contains "Initialized AgentCommunicatorApp", then continue with the steps below to resolve. Linux Monitoring Station: 1. Edit the agentcmd.jcnf file in the scripts directory of the monitoring station: In the following section:
Add:
So should now see:
2. Create a log4j.properties file in the uptime directory and populate it with the following lines.
3. Now you should be able to run the agentcmd and see only the expected output. The new extra logging lines from agentcmd are now redirected to logs/uptime_scripts.log which will rollover whenever it reaches 10mb, so it will never exceed 10mb. Windows Monitoring Station: 1. Create a agentcmd.l4j.ini file in the scripts directory of the up.time Monitoring Station with the following contents.
2. Create a log4j.properties file in the uptime directory and populate it with the following lines.
3. Wherever the agentcmd command is being called from (ie. your custom monitor script), update the agentcmd line to include the --l4j-debug option. For example, if the line looked like this:
Then you will want to change it to look like this:
|
Article InfoIndex: 600 OptionsQuick Links |
Custom monitor not matching correct output | Rating | Views | |
|---|---|---|---|
|
|
When executing your custom script from a windows monitoring station using a ".bat" file you may find that the following items need to be addressed. 1) Ensure you have "echo off" in your bat file.... By: uptime Support | Date Created: 8-13-2010 | Last Modified: 8-13-2011 | Index: 482 |
 
|
1704 |
Using the agentcmd utility | Rating | Views | |
|---|---|---|---|
|
This article provides an overview of using the agentcmd utility. By: uptime Support | Date Created: 5-3-2007 | Last Modified: 6-29-2011 | Index: 169 |
|
6095 |
Windows Event Log Monitor returns Output: Monitor failed: For inp... | Rating | Views | |
|---|---|---|---|
|
|
This error indicates that the target agent server's up.time agent is incompatible with your monitoring station version. Please upgrade the agent on the impacted server and verify that this error is... By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 497 |
|
3154 |
Enabling Audit Logging in up.time | Rating | Views | |
|---|---|---|---|
|
|
By: uptime Support | Date Created: 6-14-2006 | Last Modified: 2-27-2013 | Index: 078 |
|
3778 |
Creating Custom Service Monitors with Retained Data Collection | Rating | Views | |
|---|---|---|---|
|
|
By: uptime Support | Date Created: 5-15-2006 | Last Modified: 12-16-2011 | Index: 067 |
|
11764 |
