Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated March 31, 2017
Some Network Atlas maps either load slowly or do not load at all.
Products running on Orion Platform 2016.x-2017.1, such as
By default, Network Atlas loads every entity that can be displayed on the map and those entities's dependencies with properties and status calculations. If you have a large enough environment, the data will either be slow to load or will timeout.
You can resolve this issue in two ways:
<add key="EntitiesNotInUse" value="Orion.HardwareHealth.HardwareCategoryStatus;Orion.WirelessHeatMap.AccessPoints;Orion.NPM.CustomPollerAssignmentOnNode;Orion.NPM.CustomPollerAssignmentOnInterface;Orion.HardwareHealth.HardwareItem;Orion.HardwareHealth.HardwareInfo;Orion.DPI.Applications;Orion.IpSla.CCMMonitoring;Orion.APM.Exchange.Application;Orion.APM.IIS.Application;Orion.APM.GenericApplication;Orion.APM.SqlServerApplication;Orion.APM.Wstm.ScheduledTasksStatus;Orion.IpSla.Operations;Orion.IpSla.VoipGateways;Orion.UDT.Port">
In the example, only nodes, volumes, interfaces, and containers are loaded.
If you want to monitor applications, remove entities that being with Orion.APM from the list.
The Network Atlas maps load more quickly.