Upgrading the firmware fixed the problem.  Thanks for your help.

There's no option to clear history from the GUI, but you can delete data from database. You need to stop server process prior to deleting from the DB!!! The table you need are these two: BUSINESS_SERVICES_DOWNTIME, BUSINESS_SERVICE_TICKETS. First keeps downtime records, second keeps tickets which are displayed at the bottom when viewing a business service. Document describing the DB is here: https://www.netxms.org/documentation/datadictionary-latest/#t-business-services-downtime https://www.netxms.org/documentation/datadictionary-latest/#t-business-service-tickets

Hi Filipp thanks for that I will look to migrate our scrips over Cheers

Typically full DCI description is quite long and inconvenient to be used on links, that's why it's not displayed there by default. What we have instead is so called format string, which can be seen in properties of a data source. Format string can contain any text, so you can just put description of your DCI there. Placement of DCI value is defined by java macros. See docs for information on this: https://www.netxms.org/documentation/adminguide/visualisation.html#adding-links-between-objects

To have a table with values on a dashboard we have the following options: Object query DCI summary table We can use script to build a Table DCI and display that on the dashboard But I still do not understand how bar graphs and line graphs should work - do you want them to show data from 3 "worst" nodes?

Quotes removed: 2025.04.08 10:13:13.718 *D* [comm.cs.1          ] Requesting metric "Database.Data(foo)" 2025.04.08 10:13:13.718 *D* [dbquery            ] H_DirectQueryConfigurable: Executing query "SELECT `name` FROM `test` WHERE `description` LIKE ?;" in database "id1" Result is fine. But if I add my own text to the value (e.g. LIKE %?), an error is logged You have an error in your SQL syntax. The metric only works when I put the whole condition in the metric brackets (it must not be in the configuration file).

Thanks Amay! My problem was that I didn't realize that the last digit was the index for the interface that I wanted to monitor. I can pull proper results for the individual DCI. I just need to figure out how to setup a template to automatically pull these values.

Then we'll wait for a new patch release.  Thanks for the quick support. Regards Peter

Apparently I did not think this through. What can I do, now that I see all the unmanaged devices to disable / pause them so they do not count towards the license?

Nice to hear that

I've added chapter to the docs describing it: https://netxms.org/documentation/adminguide/user-management.html#ui-access-rules

@filipp-sudanov said in 5.2.0 dashboard rack diagram not scaled to fit element size: Yes, racks now have scaling limit so that units don't become too small. Looks like this is not ideal for dashboard use, I've created a ticket to improve that: https://track.radensolutions.com/issue/NX-2738 OK thanks.

Are these possibly still on the horizon ?  I really think this would be a good addition.  I know other NMS's have implemented it but not sure how difficult this is.  Thanks,

It works, thank you.

That's a bug, fix will be in v. 5.2 which should be out quite soon

Hi Filipp, The alarm keep coming back after 1 hours.  Appreciate if u can take look this issue. Thanks

In overall it's not recommended to increase Agent.CommandTimeout too much (like > then 5 seconds) because in situations when agents are slow to respond server will spend too much time waiting.  If your query takes too long, you can use External metric provider - in this case command is executed in the backgound and agent caches values. https://netxms.org/documentation/adminguide/agent-management.html#externalmetricprovider

Thank you for the help, I discovered in the script a section that had the potential to infinitely loop if the webservice it was accessing was offline. I fixed this oversight in the script, and moved the script to be the Event Processing action as per your first suggestion, and we haven't had the issue since. Thanks again!

On any node under Infrastructure Services there's Data Collection tab. The screenshots are from properties of a Data Collection Item (DCI) from that tab. DCIs can be specified on nodes, or in template (which should be applied to nodes). You can create your DCIs on a node to test them and move to a template later on. We have some info on data collection in the docs: https://netxms.org/documentation/adminguide/data-collection.html , but feel free to ask questions.

Simple syslog parser rule with Matching regular expression .*  and specifying the event will work. They you can add Facility and Severity filters if needed.