Comments
-
I would also like to see the ability to search for server names such as FP* and show only VMs and which host they are currently sitting on. Currently I do not see an easy consolidated way to do this.
-
Do we need to raise another request for the status implementation to be expanded or can this be followed up? This would assist us in monitoring our VMs, whereby we would like for the cpu component of a node (VM) to change to a warning/critical status, which in turn would feed up to the group and the group would then change…
-
Updated as above.
-
I was aware of how to add/create my own custom graphics but I would like to know if/how to change the size of the child status icon, where are these icons and can I resize them? Thanks Tom
-
Although typically as I typed that, I popped into Network Atlas, right clicked the node, properties and selected the metrics tab and changed the memory threshold map to Warn=98% and Critical=99% and its now turned the child object a lovely shade of "all good green"!
-
Hi ding, We are very interested in this too, as mentioned, DHCP failover is a standard feature in 2012 R2 and we are now looking to fully utilise the IPAM module, the only hold back is that Solarwinds IPAM does not support it. Can you confirm if your looking into this? Thanks
-
To update, Solarwinds support suggested running a command against the NetPerfmon db which has resolved the issue. Process as below: 1) Backup Orion DB. 2) Stop all the Solarwinds Services. 3) Run the following SQL query: DELETE FROM ActionsAssignments WHERE ActionID NOT IN (SELECT ActionID FROM Actions) 4) Restart the…
-
Oh how foolish do I feel!! Thank you designerfx!
-
Anyone from Solarwinds able to provide guidance on how to increase the size of the child led?
-
We care currently using 7.1 at the moment, with a plan to move to 8.1. Has this been resolved in either of those versions, or am I missing the setting in 7.1?
-
Revisiting this. Currently I don't seem to be able to get the child object to behave despite the following on the node: It still shows up on the map and the node page as being at a critical level, any ideas? Currently with these versions of modules installed:
