rmullal

Have you tried running the config wizard on all polling engines?

I don't have a fix, but can you roll back your DB?

When creating the alert, you want to limit the scope to specific objects like this: The above screenshot limits the alert to nodes that end in -FW. You could apply a custom property to the servers you want this alert to be applied to.

Emailed you.

What's the trigger condition look like?

We love the feature, but would like for it to support more devices as we keep adding more.

I had this issue when I upgraded as well. Try running the config wizard on all polling engines...that fixed it for me.

Is there an error message at all when you're on the component's view? this has usually been permissions issue for me.

i got it! here is the query: select e.EntityCaption as [Device], '/Orion/images/StatusIcons/Small-' + o.StatusIcon AS [_IconFor_Device], e.EntityCaption as [_LinkFor_Device], tolocal(max(ev.EventTime)) as [Down Time] , TOSTRING(HOURDIFF(tolocal(max(ev.eventtime)),getdate())/24) + ' Day(s) ' +…

You can open a case with support Submit a Ticket | SolarWinds Customer Portal in the online portal and they will update the SolarWinds MIB DB after you provide them your MIB file. You can then download the updated/master MIB file they provide you. You may find this helpful: Success Center 

alexslv​ did you find a solution for this? i'm experiencing this now.

ronmanp​ did you get an answer for this?

You should open a ticket with support, it could be a number of issues. SolarWinds Contact Us

Click on "Customize Page" on the left side. Then you should be able to delete the AppStack View.

what happens when you simulate the trigger? Click "simulate" as shown in the below screenshot: Then try testing with both "simulate" and "execute": What happens when you click each of these buttons? Keep in mind "simulate" will just give you a preview of your email. "execute" will actually send the email.

These can all be created with out of the box reports. 1. 2. Just filter that "All Nodes" resource 3. You could use something like this: 4.

Did you find anything out about this?

Did you find anything out? we are facing the same issue.