NetXMS Forum

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

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

---

NetXMS Server Configuration.xlsx

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!

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

Hi!

Is it possible to implement an "Open Incident Counter" as a Dashboard Component? For our Service Desk it would be very helpful to see how many warnings, minor, major or critical alerts are aktive at the moment.

For Example:

    5            0          2            1
Warning    Minor    Major    Critical

Additionally we would be very glad if you could tell us a solution to simply view DCI-information like "Total Disc Space" or "Service Status / Process Count" on a dashboard. Our latest try-outs with the Gauge Dashboard Component looks very weird.

Last but not least we have the following bug: Sorting of the Table Value Dashboard Component is not working. You could tap on the headerline and a little arrow up or down is shown, but nothing happens to the table rows. Could you please fix this?

Thanks in advance and best regards
Florian Mialki

Dear Gentlemen

Is there any possibility to simply view the last values of several (not all) Agent DCIs of one node? We would like to have an overview of all the system information like System time, Total space on filesystem etc. in a dashboard. (f. e. just a small table with Agent DCI description and last value)

Thanks in advance and best regards
Florian

Hi Gentlemen

I was not able to get reports working on a windows machine so far, too. Could you please post a short guide on how to implement reports module on windows machines?

Thanks in advance and best regards
Florian Mialki

Dear Gentlemen

I would appreciate an answer to Taomyn's question, too. We're getting frustrated in trying to configure a dashboard with all service status for one node. Is it possible to use the status indicator for DCIs somehow?

Thanks in advance and best regards
Florian

Hi Victor

Could you please shortly list the colours you are going to implement in release 1.2.10? I would expect the following:

Grey = Unmanaged
Green = Managed + Normal
Blue = Managed + Warning
Yellow = Managed + Minor
Orange = Managed + Major
Red = Managed + Critical

Could you please confirm or correct my expectation from above?

Thanks in advance and best regards
Florian

Hi Victor

For our use case one global configuration parameter (e.g. defaultStatusTimeout) would be satisfying. Maybe you could keep in mind to extend this feature for additionally setting this parameter individually for one of the upcoming releases after 1.2.10.

Is there any scheduled release date for 1.2.10 known, yet?

Thanks in advance and best regards
Florian

Dear NetXMS Team

Is there any simple way to modify the ICMP Status Timeout? As far as I know this is at 1500ms by default. We would like to use NetXMS for Devices connected via satellite where RTTs above 1500ms are quite normal. If there is currently no way to modify the ICMP Status Timeout, would you be so kind to implement this asap?

Thanks in advance and best regards
Florian Mialki