NetXMS Forum

Hello! It will use server time. Just fixed typo, thank you! Best regards, Victor

Hi Filipp, Thank you for the clarification! That makes me less stressed out. I was getting worried I would have to rewrite everything I've written so far.

I'll be updating this using correct syntax for NetXMS v5.0.

Thank you for the info!

Just checking in to see if this is something that is being looked at. I didn't see this added as an issue on https://track.radensolutions.com/issues yet.

Also looking forward to new grafana connector. It is normal for current one to eat up sessions, every panel and query you have that has some DCI reference will create session on page load. when page has loaded the sesssions slowly die and if you leave the page with only panel refreshes it keeps sessions low but as soon as you do side refresh in browser it start all sessions again. Been strugling for a long time with grafana eating up over 128 sessions making server unconnectable until sessions die off.

One possibility that I see is out of order execution of hook scripts which is theoretically possible. Server schedules execution of hook script in background thread pool, passing copy of alarm in its current state to the script. It is possible that due to database problems thread pool was full with tasks waiting on database, so earlier script execution task was waiting on free thread, next task was scheduled in the meantime, and then both were started in parallel, possibly in wrong order. I will think about it, but probably we have to serialize executions of alarm state change hooks. Best regards, Victor

Yes, URL field supports macros, so %[OGAckAlarmID] should work. I am not sure how you are getting alarm ID in that script, may be you should pass the ID as parameter in your PostEvent() calls. Request Data field is employed when web service is used as data source for a DCI. When using post() method of web service object, that field is ignored, so you have to pass the whole request in post() call.