NetXMS Support Forum

Hi there,

I got a little Problem after I've updated to 3.1.343, some Internal DCIs changed to UNSUPPORTED:
- From Template /NetXMS Server/Database Writer:
   - Server.AverageDBWriterQueueSize.IData;
   - Server.AverageDBWriterQueueSize.Other;
   - Server.AverageDBWriterQueueSize;
- From Template /NetXMS Server/Server Performance:
   - Server.AverageDataCollectorQueueSize;
   - Server.AverageSyslogProcessingQueueSize;
   - Server.AverageSyslogWriterQueueSize;

Today, I updated to 3.2.472, that didn't solve the problem.

Trivia:
I once manually changed these DCIs (at Node, not in the Template) to DISABLED, but everytime the housekeeper ran it reenabled the DCIs...
...the DCIs changed back to UNSUPPORTED and so I got 6 Alarms every morning.
Because I got really annoyed by those 6 daily alarms (I get most alarms via mail too, cause I'm not looking at the Console all day long), I tried to find a way to disable the DCIs for good (so I've at least got workaround).
Strangely, the TemplateGroup "NetXMS Server" wasn't visible at my installation, at the DCI Collection Configuration the Internal DCIs just showed <unkonw> at the template-column.
I took some time analyzing the Database-Structure itself and I found out there was no entry for this TemplateGroup in the table "container_members".
After manually creating that entry and restarting the NetXMS Core, the Console showed me that TemplateGroup and I could disable those DCIs in the Template itself.

As I guess, disabling DCIs in the "NetXMS Server" Templates might not be the qay the system was designed, I just wanted to ask for any ideas about what's wrong with my installation...

NetXMS Core is running on Windows Server 2008 R2 with MariaDB Database (Server is configured to use the mariadb.ddr Driver).
Prior to the Update to 3.1.343, everything was fine.

Any idea is highly appreciated!

Best regards,
Manuel

Hello,

I dunno what I'm doing wrong, but I've come across a (at least to me) mysterious problem...

I've configured an ExternalTable Parameter for all nxagents on our Windows-Hosts
ExternalTable=file.TableSubFolders(*):instanceColumns=Folder;description=SubFolders with Size and FilesCount;separator=|:powershell "echo 'Folder|Size|Count'; Get-ChildItem -Force -LiteralPath '"$1"' | foreach { $$subFolderItems = Get-ChildItem $$_.FullName -recurse -force | Where-Object {$$_.PSIsContainer -eq $$false} | Measure-Object -property Length -sum; $$Status = $$_.Name + '|' + $$subFolderItems.Sum + '|' + $$subFolderItems.Count; echo $$Status }"

That ExternalParameter will take (as an argument) a Folder-Path and return a table of all subfolders with the Size and the Count of all Files inside them...
...I'm using that to monitor the Size of our Users RoamingProfiles and HomeDirectories.

I created three DCIs using that ExternalParameter:
- RoamingProfiles Win7
- RoamingProfiles Win10 (yes, we let our Users start over with empty Profiles for Win10, hence the seperate Directory for those...)
- HomeDirectories

First I'd like to mention that the DCIs for the RoamingProfiles are working fine, while the DCI for the HomeDirectories seemingly does not work correct.

If I query those three ExternalParameter directly with NXGET-CommandlineTool I get correct output.

But if I view the "Table Last Value" in NetXMS-Console, I'll see correct Data for the RoamingProfiles-Directories, but I do not see any Data for the HomeDirectories at all...
...I attached some screenshots for illustration...

Any ideas what I might have configured wrong for the malfunctioning DCI?

Best regards,
Manuel

PS.: I've already set the ServerConfiguration-Variable AgentCommandTimeout to 59000 and the AgentConfiguration-Parameter ExecTimeout to 55000, because of that and because of the ExternalList for the RoamingProfiles taking more time (on FS01 to calculate Directory-Sizes) with NXGET I don't think it's a timeout-related problem...but feel free to correct me if I'm wrong! :-)

Search-Function in EventProcessingPolicy, so that you don't have to search in the EventProcessingPolicy all by yourself just to get to the Rule, which you wanna edit.

Being able to filter incomming syslog (regardless if it's just for storing syslog or also for the processing), would be handy, if you've got some hosts, which you cannot prevent from sending syslog for everything (including DEBUG-Severity)...
...this Filter would be handy, if you could apply it on a per node basis, as well as as global configuration.

Beeing able to configure syslog retention time also per node (deviating from the global syslog retention time configured in server configuration) would be great.
If you've got some Hosts, which are monstrously chatty with syslog, you could restrict syslog-retention time for those to a few days without throwing away the syslog-data from other devices...

Hy there,

I may just have not googled enough, but I don't know how to configure a single Threshold to fire at two given Pattern_Strings.

I've got a DCI, which returns a String.
I want the Treshold to fire when that DCI is NOT LIKE "Online" AND NOT LIKE "Ready"...

Best regards,
Manuel

PS.: If someone reading this Post wishes to have some kontext:
I'm using OMREPORT (CLI-App for Dells OMSA) to read Disk- and RAID-Status from an old PowerEdge-Server, which has got just the iDrac 6, which wouldn't give ma that information via SNMP...
...I've written a Powershell-Script to gimme a list of all pDisk-IDs (for Instance-Discovery) and another to read actual Values from OMREPORT.