<![CDATA[Event processing, Configuration File Policies and Package Manager]]>Hi all,

as we are using NetXMS for the system monitoring of our vessels, we are facing three problems with NetXMS version 1.2.9 at the moment:

  1. Event Processing: We have set the "ThresholdRepeatInterval" under Server Configuration to 0 and the "Repeat event" of all DCIs' Thresholds is set to "Use default settings". According to the Thresholds' event, an email is sent as an Action to our teammailbox. Due to using Templates for all vessels, there are a few vessels for which we are monitoring services, which are not installed yet. Against our expectations we receive an Email-Alert every week, which should be only once.

  2. Configuration File Policies: As we have a standardized structure for every vessel, some nodes are disabled for some vessels. If we try to install a policy on one of these nodes, an error occurs, because no NetXMS client is installed on the disabled nodes and therefore the necessary action is not available. This is especially tricky, when we would like to install a policy on all nodes. Maybe there is a possibility to only link disabled nodes to the policy and install the linked policies, when the node is enabled?

  3. Package Manager: Due to communication via satellite, we are facing a lot of connection issues. If we are distributing a new NetXMS Client Package via Package Manager to all of our vessels, only approx. 20% will be completed successfully. In the Package Deployment Monitor we have no possibility to restart failed deployments and if we restart the Deployment via Package Manager for all nodes, the deployment runs for every node (no matter if it has been deployed successfully before or not) again. So finally we don't have a general overview, where the packaged has been deployed successfully and where we do have to restart the deployment.

Could you please check this three issues and give us a hint, how we might optimize the situations, if there will be any improvement with a newer version of the NetXMS console (current: 1.2.10) or if you are going to plan any bug correction within one of the next versions?

Thanks a lot in advance and best regards!
Florian Mialki

]]>https://forum.netxms.org/topic/3134/event-processing-configuration-file-policies-and-package-managerRSS for NodeFri, 13 Nov 2026 12:18:10 GMTMon, 05 May 2014 07:48:12 GMT60<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Tue, 08 Jul 2014 22:51:51 GMT]]>Hi!

Bug with repeated threshold violation events was fixed in 1.2.14. I had to read our own change log first 🙂

Issue 564 is relatively easy to implement, I think I can made it before 1.2.15 release. 563 is more complicated, and most likely it will not be before 1.2.16 release.

Best regards,
Victor

]]>https://forum.netxms.org/post/14357https://forum.netxms.org/post/14357Tue, 08 Jul 2014 22:51:51 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Mon, 07 Jul 2014 11:11:54 GMT]]>Hi Victor

Could you please let me know the target version for issue 563 and 564. These features are really important for us.

Thanks in advance and best regards!
Florian

]]>https://forum.netxms.org/post/14342https://forum.netxms.org/post/14342Mon, 07 Jul 2014 11:11:54 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Fri, 09 May 2014 10:30:20 GMT]]>Hi Victor

Here you are...

  • TemplateDCI.jpg: DCI Settings for one DCI which is affected within one Template
  • TemplateDCIThreshold.jpg: Threshold config for the Template DCI above
  • NetXMS Server Configuration.xlsx: General Server Configuration
  • NodeLastValue.jpg: Last Values for one node, where you can see that an event is raised
  • Event Processing Policy.jpg: According Event Processing Policy, which is responsible for sending the email

Best regards
Florian

TemplateDCI.jpg

TemplateDCIThreshold.jpg

NetXMS Server Configuration.xlsx

NodeLastValue.jpg

Event Processing Policy.jpg

]]>https://forum.netxms.org/post/13861https://forum.netxms.org/post/13861Fri, 09 May 2014 10:30:20 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Fri, 09 May 2014 10:07:51 GMT]]>Can you please show how exactly problematic threshold looks like?

Best regards,
Victor

]]>https://forum.netxms.org/post/13860https://forum.netxms.org/post/13860Fri, 09 May 2014 10:07:51 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Fri, 09 May 2014 08:10:34 GMT]]>Hi!

It's definitely a bug - looks like threshold state was not saved across restarts, although it had to be. I'll check this.

Best regards,
Victor

]]>https://forum.netxms.org/post/13859https://forum.netxms.org/post/13859Fri, 09 May 2014 08:10:34 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Fri, 09 May 2014 07:52:39 GMT]]>Hi Victor

First of all thanks a lot for creating the two feature requests!

@victor said in Event processing, Configuration File Policies and Package Manager:

Hi!

@mialkfl said in Event processing, Configuration File Policies and Package Manager:

  1. Event Processing: We have set the "ThresholdRepeatInterval" under Server Configuration to 0 and the "Repeat event" of all DCIs' Thresholds is set to "Use default settings". According to the Thresholds' event, an email is sent as an Action to our teammailbox. Due to using Templates for all vessels, there are a few vessels for which we are monitoring services, which are not installed yet. Against our expectations we receive an Email-Alert every week, which should be only once.

Could it be that you re-apply templates periodically? Is it some fixed interval or you get these events at random moments?

No, we are not re-applying templates periodically. But what we found out is, that the NetXMS Server has been restarted less than 1 hour before the Events and Emails has been resent. From our point of view it seems to be a bug, because if I don't want Events to be resent, this should be restart resistent.

Thanks in advance!

]]>https://forum.netxms.org/post/13858https://forum.netxms.org/post/13858Fri, 09 May 2014 07:52:39 GMT<![CDATA[Reply to Event processing, Configuration File Policies and Package Manager on Wed, 07 May 2014 15:30:29 GMT]]>Hi!

@mialkfl said in Event processing, Configuration File Policies and Package Manager:

  1. Event Processing: We have set the "ThresholdRepeatInterval" under Server Configuration to 0 and the "Repeat event" of all DCIs' Thresholds is set to "Use default settings". According to the Thresholds' event, an email is sent as an Action to our teammailbox. Due to using Templates for all vessels, there are a few vessels for which we are monitoring services, which are not installed yet. Against our expectations we receive an Email-Alert every week, which should be only once.

Could it be that you re-apply templates periodically? Is it some fixed interval or you get these events at random moments?

@mialkfl said in Event processing, Configuration File Policies and Package Manager:

  1. Configuration File Policies: As we have a standardized structure for every vessel, some nodes are disabled for some vessels. If we try to install a policy on one of these nodes, an error occurs, because no NetXMS client is installed on the disabled nodes and therefore the necessary action is not available. This is especially tricky, when we would like to install a policy on all nodes. Maybe there is a possibility to only link disabled nodes to the policy and install the linked policies, when the node is enabled?

  2. Package Manager: Due to communication via satellite, we are facing a lot of connection issues. If we are distributing a new NetXMS Client Package via Package Manager to all of our vessels, only approx. 20% will be completed successfully. In the Package Deployment Monitor we have no possibility to restart failed deployments and if we restart the Deployment via Package Manager for all nodes, the deployment runs for every node (no matter if it has been deployed successfully before or not) again. So finally we don't have a general overview, where the packaged has been deployed successfully and where we do have to restart the deployment.

Both are possible. I've created feature requests for them:

https://www.radensolutions.com/chiliproject/issues/563
https://www.radensolutions.com/chiliproject/issues/564

Best regards,
Victor

]]>https://forum.netxms.org/post/13819https://forum.netxms.org/post/13819Wed, 07 May 2014 15:30:29 GMT