Thanks I missed this when reading the manual. This feature does what I want know I know how to use it.

Ok, I found the error. My functional agent config: #System Shutdown with delay EnableActions = yes Action = System.ShutdownWithDelay:shutdown.exe -s -c "PowerFail" -t $1 Action = System.ShutdownAbort:shutdown.exe -a I added the abort command for Shutdown.

Thankyou for replying, it turns out that my agent wasn't working correctly, I applied it to another agent and it worked ok, just had to reinstall the agent. I was going to reply to say it was fixed but was very sick yesterday Thankyou once again. Great product. Good luck with the business.

When you query Icmp.* parameters, you should be asked for additional arguments. For Icmp.Ping, you should enter IP address you wish to ping. Agent should do ping to given address respond with ping response time. For all other Icmp.* parameters you should specify name or IP address of preconfigured target. See this document: https://www.netxms.org/documentation/ping_subagent.shtml. Best regards, Victor

Yes, you right - alarm message is unavailable within script. For the next version, I add new global variable $alarmMessage which will hold alarm's text. It's not part of event object (it's only created based on event data), so it will be incorrect and technically slightly harder to put it as $event attribute. Currently you able to pass alarm message to action via %A macro - this can help if you don't need it in script. @jdl said in Actions - Parameter?: In the script, the $event->message refers to the text message defined in the event not in the alarm which can be more specific as we get additional macro's at that level, right? You have only two additional macros at alarm definition level - %m (event's message text) and %M (custom message, if set in matching script). All other macros are the same (including scripts and custom node attributes). Best regards, Victor

Server should not crash - it's a bug. But anyway, when script returns something to be used as macro expansion result, it should be string. Best regards, Victor

HI All, I want to monitor the following 1.Monitor (ping) servers and send out alerts if they are not responding. 2.Monitor (HTTP)  ESB processes and Portal processes and send out email alerts if no response. 3 .Monitor database tablespace and send out alerts if free space on some of the tablespaces goes below certain limit. i tried with standard parameters but it not fulfilling my  requirements.please me help out How to create the custom parameter list ? How to catch error in the esb logs and send out a  alert email ? Server version :0.2.26 agent version :0.2.26 Thanks Pasupuleti

Please try updated version attached here: https://www.netxms.org/forum/index.php/topic,670.0.html Best regards, Victor

Hi all! Attached is updated logwatch subagent (for 32 bit Windows). All outstanding issues with Windows event log monitoring should be fixed - it should work with Security log and custom application logs, and Windows 2008 related problems should be fixed as well. I'll be very appreciated if someone test it on different platforms and logs. You can simply replace old logwatch.nsm in 0.2.26 agent with attached one. Best regards, Victor

Hi! Probably it's currently better solution, but a bit inaccurate - status can change not only because node is down, but also if one of the interfaces goes down, or if you have active alarm for that node (as a result of threshold violation, for example). You at least should set threshold to "equals 4" instead of "greater than 0", because 4 is status code for CRITICAL status, so at least you will not send notification if node, for example, go to MINOR status due to an alarm. You can also avoid false positives when node's status is CRITICAL, but it is not down, but in a quite complicated way. You can create situation (in View -> Situations), and update it on each NODE_DOWN and NODE_UP. For example, on NODE_DOWN set "down" attribute to 1, and on NODE_UP, set it to 0. Then, add additional check using script to notification rule, to check stat situation's attribute "down" is set to 1. Best regards, Victor

Hello! It depends on log file and platform. On UNIX, size of monitored file checked once per second. If size was changed, log parser reads and processes new data. If new size is less than previous, parser assumes that file was cleared, and reads it from the beginning. On Windows, processing is different for text files and Windows event log. For text files, parser subscribes to file system change notifications (using FindFirstChangeNotification/FindNextChangeNotification API), and when change is detected, processes file in the same manner as on UNIX. For Windows event logs, parser opens them via Windows event log API and waits for changes. When new records added to the log, parser gets notified and processes new records. And starting from 0.2.27 release, parser uses different API for Windows Vista and Windows 2008 - this should solve various event log parsing problems on these systems. Best regards, Victor

Are there any?  I want to start the NetXMS console in object browser mode from a start menu icon. Thanks! Trent

I did get an event 2019 in the Windows Application log SNMP Event Log Extension Agent did not initialize correctly. There was also Event ID 3003: Error positioning to end of log file -- can't get oldest log record. Handle specified is 14090292. Return code from GetOldestEventLogRecord is 223.

Hi! Looks like server bug. What nodes as duplicated? For example, node with IP 40.16.1.2 - what it is, how it's interface list looks like? (You can send this info to [email protected] if you don't wish to disclose this information on forum). Best regards, Victor

Lines started with * character defines a new config section (usually subagent configuration) - and parameters allowed in each section are specific to this section. Core agent parameters should be defined in "default" section - unnamed section in the beginning of the file. Order within section is not important. Best regards, Victor

Yes, it's a bug. Added it to bug tracker (#256). Best regards, Victor

wow we are really hope you rignt, Victor

Hello, I implemented a log file parser to catch messages when an user is (connected / disconnected) (to / from) an application running on the node. When an user is connected or disconnected, an event with the user id is generated. What I would like to do now is to graph the number of connection to the application by using the parser and implement a kind of counter. When the parser catch the message that an user connects to the application, I would like to increment a counter and vice versa, when the parser catch the message that the same user disconnects from the application, I would like to decrement the counter. And after, I would like to graph this counter. For this, I need to get the last value of the counter, increment or decrement the value and store the new value. I do not find the way how to do it. I am opened to all suggestions. Thanks for your support. Regards, F.

Victor, Problem solved Thanks, //Marcel

Yes. "Process.CountEx(".*"," node_agent")" and (".*","  ./node_agent") works fine. But, (".*"," \\./node_agent") not works. (Don't care) Thanks. Regards.