nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Alert Engine Beta

jonchill

The new alert engine is so much more flexible and usable but one aspect that it does fall down on is it's macros, it now does not even put any basic macro in the outbound alert you have to look them all up.

But what might of been an even bigger benefit and made the product almost perfect is a drop down list of all the different macros type you can select then just select them from the list and place them in the alert where required, rather than having to look them up all the time. Similar to how our ISS Preventia IDS appliance allows you to build alerts from a drop down list of all available macros.

Where has the test alert feature gone?

Thanks

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

Find more posts tagged with

Accepted answers

All comments

cherrypicker

quote:Originally posted by RyanJett

quote:Originally posted by cherrypicker

Nice to have...

Orion should have to ability to monitor Windows event logs? It would be nice if it can be incorporated into the alerting engine as well.

Any thoughts?

CP

There is a free add-on utility that can be installed on Windows Servers that forwards the Event Logs via Syslog Messages. This can be downloaded in the Customer Area of the SolarWinds website. Once logged in, go to Additional Components for Orion, and download the Windows Event Log Forwarder.

Ryan Jett
SolarWinds.Net
918-307-8100

Is there a similar utility for Unix, Linux and Solaris boxes?

pblatz

quote:Originally posted by cherrypicker

quote:Originally posted by RyanJett

quote:Originally posted by cherrypicker

Nice to have...

Orion should have to ability to monitor Windows event logs? It would be nice if it can be incorporated into the alerting engine as well.

Any thoughts?

CP

There is a free add-on utility that can be installed on Windows Servers that forwards the Event Logs via Syslog Messages. This can be downloaded in the Customer Area of the SolarWinds website. Once logged in, go to Additional Components for Orion, and download the Windows Event Log Forwarder.

Ryan Jett
SolarWinds.Net
918-307-8100

Is there a similar utility for Unix, Linux and Solaris boxes?

CP
Here are the basic steps. the specifics will depend upon versions of Unix, Linux, and Solaris.

Set the ORION box up in your /etc/hosts file as the loghost
x.y.z.h orion loghost

Then edit the syslog.conf file to send syslogs of desired severity to the loghost.

Thanks,
P. B.

Success requires three bones--wishbone, backbone and funnybone. Kobi Yamada

chapter29

quote:Originally posted by casmith32

What about dependencies ? I would be great to have the ability to create device groups, then assign dependencies to the group as a whole - i.e. all switches behind a router at a site are dependant on the router. Then have the option to have alerting set to not alert on the nodes dependant on another node... i.e. if router x goes down, automatically do not alert on all the nodes dependant on that node.

will this ever happen ? it's a real pain to have to setup an alert and it's supression for every site I have, as well as dependencies within that site for larger locations. I'd like to see this simplified. that way if I add a switch or any other node to a group - I know it's automatically going to be covered in an alert that's already been created, vs having to go update the alert each time.

I imagine this grouping capability could also be applied to numerous other functionality within orion - view limitations, reporting, etc...

This question does not appear to have been answered, so I will bump it.

We are evaluating Orion as a replacement to What's Up Gold. What's up has recently released their pro version, which now uses SQL, but is still severely lacking in it's reporting and presentation. Their polling can be up/down dependant, not only the alerting.

This is a major flaw to Orion and although it appears to be a better product on many levels, alerting is a huge factor in a product of this type.

There are several other flaws that I see when comparing the 2 products, but this is not the thread for that discussion.

Network_Guru

Hey Chapter 15+14,

I think you will find a solution in this post:

www2.solarwinds.net/.../topic.asp

-=Cheers=-
NG

chapter29

quote:Originally posted by Network_Guru

Hey Chapter 15+14,

I think you will find a solution in this post:

www2.solarwinds.net/.../topic.asp

-=Cheers=-
NG

Thanks for the reply Guru.

We have approached this in a similar way, using subnets. Essentially saying if anything in subnets X or Y are down AND the router is down suppress the alert.

This will have to be timed I would guess with the router for example, being polled at a faster rate then the other devices to avoid erroneous alerting.

The issue at hand is that we have roughly 200 sites with several device types at a given site, thus requiring the need to have what I can tell a minimum of 5 or 6 alert definitions per site. One per device type (IE sending alerts to the group that manages the given device), and a suppression alert. This can be signifigantly more if we need to send to different teams based on time of day (IE on call).

Orion severely lacks some basic functionality in my opinion. Groupings. Polling sequencing off of these groupings, with dependencies (IE forget alerting, up/down polling dependencies, then alert). Why continue to poll devices that we know are down? For example, if we know that the router at a given site is down, do not even bother to try and poll devices that are up dependant on it? And the finally generic alert definitions that can pinned to a group.

This is something that quite frankly WUP does much better then Orion.

I will continue to look for ways to stream line this and make it more effective, but creating 1000 plus alert definitions is simply a poor solution, though be it perhaps the only solution.