Thanks Victor, I made some test, it looks that logged message is incomplete in some way as You wrote. This is application bug, not NetXMS and I was looking for workaround. Best regards, Grzegorz.

Repeat events for table thresholds not implemented yet. Best regards, Victor

Hi, currently not. You can add feature request for that. Best regards, Victor

Something like this should work under Windows if you run it inside PowerShell and in the actual directory holding the MIBs. Otherwise you'll have to pass the full path  to Get-ChildItem instead of *.txt. ForEach ($file in Get-ChildItem *.txt ) { Get-Content $file |Select-String -Pattern "^RFC-1215 DEFINITIONS" }

Sure were. I wasn't aware that the server crashing, deleting of wrong DCIs and DCI duplication were all related to the same underlying problem with instances. I just upgraded to version 2.0.5 and did another round of template consolidation, which included removing a number of instances from templates and the system has been stable with no odd DCI deletions either. Thanks Victor! Cheers

Sorry, haven't seen that before other. Maybe someone else has?

Thanks.  That's kind of what I thought.

Thank you, wasn't sure where that was.

Hey, I had a Network Map, the Objects explorer, Object Details, and the Alarm Browser up.

Great news that this is coming and I can wait for that feature.

Hi, do you use instance discovery in those templates? If yes, try version 2.0.5 - there were fixes in instance discovery. Best regards, Victor

for some reason it works now.... But no idea why, changed nothing

Thanks Victor

"Locked by the server." means that there is mark that database is locked in NetXMS database in config table. This can be in two situations - if server was stopped incorrectly or if NetXMS server is currently running. This flag is used to prevent change of the database while server is running (this action can be unsafe).

Hi, you should not modify anything in database directly while server is running. Server caches lot of information in memory and do not expect changes in database. They will be either ignored or even rewritten. You should use Java API or Python scripts (nxshell) to manipulate data in NetXMS programmatically. Best regards, Victor

As the node on FindObject does not limit the search scope, I implemented this using the suggested GetNodeInterfaces loop. Works fine.

For DCI scripts that are available on github and other places, how do you import them into NetXMS? Simply put the script with "chmod a+x script.sh" on the host and put it as a parameter for NetXMS to check? It seems NetXMS already has a load of pre-set checks. Thanks.

Thank you for your help. I'll take a look at this information and see what I can get of it. Greetings.

Вариантов много, например: * DCI PUSH через netxms-client (JAVA API) *  Сделать свое расширение для java subagent (пример: https://git.netxms.org/public/netxms.git/tree/refs/heads/develop:/src/agent/subagents/java/sample?js=1) * Складывать статистику в базу и вычитывать через DBQUERY * Складывать статистику в файл и вычитывать через ExternalParameterProvider (https://wiki.netxms.org/wiki/ExternalParametersProvider)

it's possible to use HEAD parameter in ServiceCheck.HTTP request? If possible, with the HEAD method to minimize traffic, bringing only the header. Tks!