Can we change the priority for the individual servers in the same alert?

Hi All,

I need suggestion if we can get the different severities for the different servers in the same alert.

for example: consider a node down alert, and there are 2 servers, prod and non - prod servers, the alert will trigger when one of these goes down with the severity which we have set, but I need a warning severity for non - prod and critical severity for prod server, is this possible? Please let me know.

I want to know is there any other way to achieve this without creating an extra alert only because of the severity.

I'm looking for a script for this case, please suggest some ideas, I'm sure we can achieve this via script.

Find more posts tagged with

severity

Alerts

Comments

vinay.by

If you are passing the severity from 'Severity of the alert' no it cannot be done. You will need to create 2 alerts one for Prod and one for Non-Prod.

But if you are forming the severity on the trigger action - custom severity - then yes it is possible using custom attributes on node level. Hope it helps.

__PRESENT__PRESENT__PRESENT

Devaraju

Hi Vinay,

Yes, I thought to pass the severity through the trigger action by creating the node custom property for the severity, but our ServiceNow team wanted to check can we able to pass directly from the "severity of the alert"

thanks for the suggestion.

can I know how many alerts in your environment and how many servers are monitored? what should be the maximum alerts in any environment to maintain a clean and clear environment.

vinay.by

Honestly its been a while I worked with ServiceNow and SolarWinds, but then if you are using the standard ServiceNow Integration with SolarWinds in that case I guess it uses "Severity of alert" and there's not much we can do about that and we will need to go with 2 separate alerts.

If you are talking about best practices for alerts (in that case):

1. I would suggest you to go back to the drawing board and re-analyze your complete environment first.

2. Keep alerts generic so that its easy to manage plus its standardized, rather than having 100s of alerts all over the place.

3. Use built in functionality and create smart alerts using the existing features of SolarWinds like CPU critical/warning threshold, Memory critical/warning threshold, custom attributes (you can use a single custom attribute for all your needs or multiple based on your need).

4. If you are asking me how many alerts should I have - then wrap up everything with as little as possible - What is it that you are looking for it would be Node Down, CPU, Memory, Disk, Interface Down, Interface bandwidth, Interface Errors or Discards, Neighbor alerts, Hardware sensor alerts, Stack members etc which NPM can offer (try to keep things simple and play around with existing functionality as mentioned in point 3). This would be easy to manage and maintain and you will know exactly why, what and how things work.

Hope this helps.

Devaraju

Thanks vinay, I have few challenges like we have created 2 to 3 alerts for a single node down alert, because few servers will shut down for a period of time in the non - business hours, there are multiple sets of servers going to shut down in different timings, so to avoid putting them into maintenance daily manually we have scheduled the alerts itself, but it resulted in creating multiple alerts. so, in these cases what would you suggest?

adam.beedell

I can confirm both these options work (Severity per alert category, severity per object), if using the OOTB SNOW integration you need SNOW to have the priority field not be too locked down to do the latter without some extra effort on one end or the other

Devaraju

Hi Adam,

Sorry, I didn't get you. where can we customize this? and we are using the ITOM event management module in servicenow. can you please explain.