Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

will unconverted alerts still work after SAM upgrade 6.1 to 6.2 ?

Needing to pull the trigger on SAM 6.1.1 upgrade. Only SAM server and additional poller. Nothing else.

However I have 134 current alerts, mostly configured as custom SQL scripts.

I understand that the alert conversion to the new web based alert manager may not work for some/all of my alerts.

My question is, will any unconverted alerts still work as they did before the upgrade?

Seems to be the case (that they will continue to work and managed in the old Advanced Alert manager, based on this thread

Re: Alerts disapeared from Advanced Alert Manager

Is this the main gotcha in the upgrade? Seems like just backup DB, upgrade to 6.2.3, apply hotfix 4 and see where I'm at.

And what are the new alerts enabled by default ? Who do they notify? I don't want to start spamming the notification groups.

Appreciate everyones insight,

Devon

Find more posts tagged with

unconverted alerts sam 6.2

Accepted answers

aLTeReGo

By default the Legacy Advanced Alert Manager disables/removes any alerts which have been successfully converted. Usually the only alerts which don't migrate are those that are broken and weren't functioning in the legacy Advanced Alert Manager anyway. If for some reason a legitimate alert is not migrated for whatever reason, you can either recreate the alert in the Web Based Alert Manager, or continue to run that alert from the legacy Advanced Alert Manager. The two alert managers are not mutually exclusive to one another. They can run in parallel until such time as the legacy Advanced Alert Manager is eventually removed from Orion in some future release.

All comments

dirwin1

actually it looks like the hotfix name has changed.to SolarWinds Orion Platform 2015.1.3 Hotfix 1

aLTeReGo

dirwin1

Thank you for the confirmation, alterego.

dirwin1

One more question to better understand this ...

I ran the upgrade on a development server and my custom SQL query alerts migrated successfully.

But when I looked at them, expecting the table names to be different, they were unchanged.

And looking at the SELECT statement - I checked and there is no longer a Nodes table.

How is this working? (I tested and it alerts if I lower memory value)

Thanks,

Devon

dirwin1

Just to answer my question in this thread for others.

SolarWinds Support told me that the old Nodes table is now referenced as a view - so these old custom sql alerts continue to work.

I was confused because all my alerts were migrated successfully, but when I looked at them they all looked the same.

I was expecting the table names to be updated.

Only question now is - (ok well 2)

Will this nodes view go away in future releases? Will I still need to eventually migrate my alerts with old table references to current?

Devon