normaette

This is a fantastic idea!

I completely agree! Excellent idea!

I completely agree! Re-deploying a test environment every 30 days is impossible for me! I have licenses for 100 NPM nodes and 150 SAM elements for basic testing, but in addition to unlimited licenses for NPM (SLX) and SAM (ALX) my prod system also uses IPAM, WPM, SRM, NCM, UDT and VMAN,and we just don't have the budget for…

Bump

Thank you @"RaviK" . @"dgsmith80", It does replace it, but only until the next time there is any update or change that requires running the configuration wizard, which overwrites my custom logo file with the original default report logo file and I am back to square 1. In addition to my Primary servers, I have seven AWS…

Next time try something complex but easy to remember like 'hard24get!'

I was able to accomplish this fairly easily by using Custom Properties. Step 1- create a custom property for volumes called 'MuteAlerts' (or something similar) Step 2- for any volumes that you want to mute alerts, set the property to True (Yes) Step 3- modify your alert to only include volumes that have the MuteAlerts…

Even if it looks like it is running fine on the server, ask the server team to restart the agent service.

I know this is kind of late but in case you were still curious, here is the trigger condition that @pflanz asked about two years ago: Trigger Condition: Edit The actual trigger condition: All child conditions must be satisfied (AND) Nodes Custom Properties - b01_PrimaryPlatform - is equal to - Windows Volumes Custom…

When I set the alert type to component, I was able to include ${N=SwisEntity;M=ComponentAlert.ComponentMessage} which had the data I wanted. Unfortunately, the names of all of the other the variables changed, but nothing that a little find and replace couldn't handle. Thanks for the help!

I know, I was hoping maybe someone found a work around- I have created a special menu bar with special views, but can't find a way to remove the settings menu.

I just at a ticket where our F5 was throwing hundreds of the same error messages and resolved it by listing the resources and changing the polling for 'Node Details' to 'Node Details by SolarWinds' from 'F5 by SolarWinds'.

Here is a very basic logical diagram you can use as a starting point, and then update the ports based on your environment.