<![CDATA[Custom Schedule query]]>I have setup an average ping time DCI for one of our sites that has a poor network connection and set it to email if the Average pings for the last 5 collections is over 1 second. This works perfectly but keeps emailing us in the early hours when the backup runs across the network. I tried to set up a custom schedule to just collect data in the day using rows like the following:

*/1 9 * * *
*/1 10 * * *
*/1 11 * * *
..
..
..
*/1 17 * * *

This doesn't work however and the schedule disappears after a few minutes. Is there a way I can just collect every minute between say 9 and 5 or 9 and 6?

]]>https://forum.netxms.org/topic/2100/custom-schedule-queryRSS for NodeFri, 13 Nov 2026 11:36:29 GMTFri, 04 Jan 2013 10:09:29 GMT60<![CDATA[Reply to Custom Schedule query on Fri, 18 Jan 2013 09:17:43 GMT]]>Answer: https://www.netxms.org/forum/configuration/custom-schedule-disappearing/msg9376/#msg9376

]]>https://forum.netxms.org/post/9388https://forum.netxms.org/post/9388Fri, 18 Jan 2013 09:17:43 GMT<![CDATA[Reply to Custom Schedule query on Sun, 06 Jan 2013 09:21:38 GMT]]>@victor said in Custom Schedule query:

Hi!

What you mean by "disappeared"? It stops collecting data, or configured schedule really disappears from DCI configuration?

Best regards,
Victor

It really disappears from DCI configuration. It seems to stay for the first few minutes but then goes completely

]]>https://forum.netxms.org/post/9249https://forum.netxms.org/post/9249Sun, 06 Jan 2013 09:21:38 GMT<![CDATA[Reply to Custom Schedule query on Fri, 04 Jan 2013 14:47:51 GMT]]>Hi!

What you mean by "disappeared"? It stops collecting data, or configured schedule really disappears from DCI configuration?

Best regards,
Victor

]]>https://forum.netxms.org/post/9246https://forum.netxms.org/post/9246Fri, 04 Jan 2013 14:47:51 GMT<![CDATA[Reply to Custom Schedule query on Fri, 04 Jan 2013 13:34:17 GMT]]>I'd guess that the custom scheduler doesn't affect/work on the average PING-agent(?).

An alternative solution could be to write a filter script in the Event Processing Policy that only allows alarms between 9am and 5/6pm. Then you wouldn't lose the statistics.

]]>https://forum.netxms.org/post/9245https://forum.netxms.org/post/9245Fri, 04 Jan 2013 13:34:17 GMT<![CDATA[Reply to Custom Schedule query on Fri, 04 Jan 2013 11:14:31 GMT]]>That didn't work either - just disappeared after 3 or 4 minutes

]]>https://forum.netxms.org/post/9243https://forum.netxms.org/post/9243Fri, 04 Jan 2013 11:14:31 GMT<![CDATA[Reply to Custom Schedule query on Fri, 04 Jan 2013 11:11:10 GMT]]>Actually I've just tried * 9,10,11,12,13,14,15,16 * * * after reading the Wiki page on cron - hopefully this will work

]]>https://forum.netxms.org/post/9242https://forum.netxms.org/post/9242Fri, 04 Jan 2013 11:11:10 GMT