Hi,
maybe someone can give me some advice for this problem.
I have several Azure AVDs I' monitoring with NetXMS, which in general is working fine.
We use FSLogiix to manage the user profiles, which is Microsoft's recommended way.
FSLogix stores the profile in VHDX file (Hard drive image) which is then mounted when the user logs on
and dismounted on logoff. And here is my problem.
NetXMS recognizes when a drive gets mounted or dismounted, which in general is a good thing.
I my case it results in a crazy high number of DCIs (see screenshot), some active some disabled.
Is there a way to avoid this? I only want to monitor the fixed drives of the server.
Also, why is it showing a Template with the same name as the host for this DCIs?
Thanks for Your help
			
			
			
				These items are from standard template "Operating Systems/Windows".
this template create two metrics related to file system (FileSystem.FreePerc({instance}) and FileSystem.UsedPerc({instance})), both with enabled instance discovery.
More information on instance discovery: https://netxms.org/documentation/adminguide/data-collection.html#instance
Short summary: system query FileSystem.MountPoints from the agent to get all available mount points and create (or delete) new DCI for each instance. Since it's done in the context of the node, template column is set to the node itself.
In instance discovery, there is a filter, which can return true or false: create or ignore.
Default filter in the template add anything except CDFS.
There are multiple solutions, simplest is:
1) create new template, configure automatic apply, like in the original template
2) disable existing DCIs in the "Operating Systems/Windows" template. Status change is persisted even when we update system templates.
3) copy these DCIs to the new template and adjust instance discovery filter to your liking.
We plan to implement small changes to the scripting language which will allow creating hooks for standard templates, but for now you'll have to modify them.
			
			
			
				Thank You very much. I really appreciate the comprehensive explanation.