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

Alarms to different mail

dAnTeDK

Hi,

I’m struggling with the creation of some alarms.

The setup:

- It’s a Docsis setup.

- A CMTS(Docsis router) has different Technicians pr upstream.

- Each Tech has his own email.

- The internal Tech’s must receive an email with a link to Orion, the external Techs must receive an email without a link to Orion (too much classified info for them).

- There’s about 100 sites total, all with multiple different Technicians, for their specific geographical area.

The trigger:

For example if the upstream SNR goes below 25db it triggers the alarm. On upstream 0 it somehow knows it’s an internal tech and on upstream 1 it knows it’s an external tech. So it sends different mails as explained above.

I can’t seem to find a way to create a rule (or 2) that interconnects all my demands in an easy manageable way.

I’m not going to explain how I’ve been trying to do this, partly because it’s was too comprehensive to manage and I don’t want to color your way of thinking.

Any suggestions, as to how it’s done?

Regards

Find more posts tagged with

Accepted answers

All comments

mcbridea

Take a look at this blog post - I think this trick would help a lot.

robertcbrowning

The link to the blog shows how to use variables for the mail adresses, but you may also want to use Custom Properties to group your alerts into, say, Internal or External to establish whether or not to include the URL to Orion.

dAnTeDK

Here's what I've done so far:

I use an variable for the email adresses.

I created 2 alarms, one for internal (with link)and one for external (without link).

I created 1 Custom properties for the node called ExternService (yes/no type)

I created 1 Custom properties for the interface called EksternServiceInt (yes/no type)

Below is an example of the internal alarm created:

Below is an example of the external alarm:

ebradford

I think I may have the answer you are looking for. The answer resides not in Orion, but in your e-mail server. Create proxy addresses which forward to the correct technician's e-mail. You would then use the node id and/or interface id in the e-mail address to identify the proxy.

Example: Jon W at ServiceInc. is the enternal technician for a the Fa 0/2/0 interace with ID=751 on a c3845 router with node ID = 92.

You send the External Alert to tech.${Interface.InterfaceID}@yourcorp.com the alert goes to tech.751@yourcorp.com. You then have your e-mail server forward tech.751@yourcorp.com emails to jonw@serviceinc.com.

Since interface IDs are unique, you could use one alert to send to one of 1000's of addresses. You would have to configure a proxy address for each one though.

Since you are using custom interface pollers (I love your use of it), you'll need to use the ${Interface.InterfaceID} variable instead of ${InterfaceID}.

I mentioned the ${NodeID} variable above because some people may find it useful in some instances, but it doesn't to use it. However, for a node, the custom property "primary contact" would be easier. Anyway, please try this and let me know if it solves your quandry.

Eric