I've recently found out that there are a number of alerts configured with a sender address that is being blocked by Footprints, thus keeping our NOC from getting tickets for these alerts. When I look in the Database Manager I'm seeing 263 instances of this. I am not very well versed with SQL, and would like to update/replace all instances of "noreply@solarWinds" with a different sender address.What would be the best way to go about this?
@ZombieEtiquette, you can mass edit Alert Actions of the same type, which would probably be a little safer than doing a direct DB edit. Just select all the offending Email Actions and update them to the appropriate values, you can also use variables so that they pull them from the Default Send Email Action Page. Should look like below
You are likely just using the default, go to the All Settings -> Configure Default Send Email Action and update it with your information:
Run the query again after and lets see if you need to update anything.
Thank you. This is helpful. I went ahead and updated this to make sure there are no more issues going forward with any newly created alerts. However, I did run the query again (as well as checked the trigger actions for some of the alerts I know are affected by this) and they still have the problematic reply address.
