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
- SolarWinds Academy
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

Alarm Segregation between multiple teams

thangaselvi

Hi All,

How to segregate the OOB alerts to different team based on the custom property for SNOW assignment groups and mails.

Assume we have NODE DOWN alert where it been monitored for all nodes, in this case i have a custom property called tenant with customer A and customer B values according to their devices .

In this case with the customer A device is down i need the alert to be mailed for cus A mail ID and trigger the SNOW ticket for cus A group.

It is possible to do in OOB alert policy or disable the OOB policy and make the own alert policy with custom property filter ?

Any suggestion

Find more posts tagged with

npm

Comments

stuartd

He already has the CP's.

vinay.by

Hi @thangaselvi

Easiest approach would be to create custom properties for this and use that in your trigger action as a variable.

stuartd

First off, you won't be able to edit the OOB alert so you will need to duplicate and edit.

Secondly, presuming I've understood the ask, the easiest way is to utilise the custom property you've created. I'm not in front of a setup now to 100% advise and the alert logic would be something like:

If node = down
AND
Custom Property = Tenant and Value = CustomerA

Then in the mail section you simply set it to trigger to send the alert to the customer / team.

You would then duplicate this and adjust for Customer B.

Alternatively, you can specify the target(s) that the alert would apply to, and select all nodes for Customer_A. Again, duplicate and adjust for Customer_B.

thangaselvi

Thanks , but how the email with be sent to customer A based on there device with help of custom property value .. i dont see anywhere the variable to be added.

bourlis

Hi thangaselvi,

It's not 100% clear on what asking, so please excuse me if I answer incorrectly.

For SolarWinds Observability Self-Hosted or NPM, yes, you can create custom trigger actions that do all sorts of things. The caveat being you need a rigid trigger condition.

Case in point.

Trigger condition
- Scope of alert <and>
  - Node custom property 'customer' = Customer A
  - Node custom property 'email' = CustomerA@company.com
  - Node custom property 'SNOW' = SNOWId
- Actual trigger condition
  - Node status = down
Trigger Action
- Action #1 email
- Action#2 SNOW action

Repeat this for customer B.

For your email you can use this as an example, note Primary_Contact & Node_Alt_Contact are my custom properties for email addresses

A baseline for your email can look like this:

Technically you can use this same alert for both custom A and B if build it out correctly.

For the second trigge action you can do this, not this is for PagerDuty… but you can get an idea.

{

  "payload": {

"summary": "Alert: ${NodeName} - ${N=SwisEntity;M=IP_Address} is ${N=SwisEntity;M=Status}.",

"class": "${N=SwisEntity;M=CustomProperties._Disposition}",

"source": "${N=SwisEntity;M=CustomProperties.PDUrgency}",

"component": "${N=SwisEntity;M=CustomProperties.Notification_Profile}",

"group": "${N=SwisEntity;M=CustomProperties.ITD_Responsible_Team}",

"severity": "critical",

    "custom_details": {

	"Node": "${NodeName}",

	"Status": "${N=SwisEntity;M=Status}",

	"Location": "${N=SwisEntity;M=Location}",

	"Machine Type": "${N=SwisEntity;M=MachineType}"

    }

  },

"routing_key": "${N=SwisEntity;M=CustomProperties.PDIntegrationKey}",

"dedup_key": "${N=SwisEntity;M=NodeID}",

"event_action": "trigger",

"client": "SolarWinds ${N=Generic;M=Version}",

"client_url": "${N=SwisEntity;M=DetailsUrl}"

}

I hope this helps!

Quick Links

Dynamic Interface Dashboard; HTML/JS
I wanted to share a new dashboard a co-worker ( @mblackburn ) came up with to help us better view groups of interfaces and various metrics for each. Using a single HTML widget, we are able to visually compare numerous different interfaces by populating each interface dataset onto its own graph. We are able to view…
PALO-ALG - Logging
PALO-ALG - Logging.xmlPalo Alto Networks ALG Security Technical Implementation Guide :: Version 2, Release: 3 Benchmark Date: 27 Oct 2022
Alert HTML Content
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices
Cisco ASR Devices.pollerCisco ASR Devices