Forwarding alarm events via TCP-IP sockets (unsolicited)

283 viewsalarms forwarding
2
1 Comment

According to the documentation, it is possible to forward alarm events using TCP-IP sockets. Here is what I found:

I would like to know:

  1. Is it possible to assign alarm filters to determine what events are sent out?
  2. Is it possible to define more than one AlarmSocket in the DataMiner.xml config file? Each socket would be used to send alarm events to different 3rd party applications based on different alarm filters (see first question)

Thanks

Pieter Van Compernolle [SLC] [DevOps Enabler] Answered question 13th September 2024
Alberto De Luca [DevOps Enabler] commented

Great use case – was looking into something similar – so I’ll subscribe (;
Filtering is not explicitly mentioned as far as I know.

In my previous approach, I had discarded the TCP socket option as I need also alarms coming from the correlation engine, and I understand that’s not supported via TCP sockets:

“Only raw alarms are forwarded via TCP/IP sockets. Alarm messages generated by the DataMiner Correlation engine, for example, are not forwarded via TCP/IP sockets.”

I’m led to think filters aren’t either, as they are normally synchronized in the DMS, while the “The DataMiner.xml file is not synchronized throughout the DataMiner System. It is unique for each DMA. As a result, you can have different socket configurations on each of your DMAs.”

An alternative may be this other approach based on SNMP “Inform”
https://community.dataminer.services/question/good-approach-to-guarantee-snmp-traps-as-much-as-possible/?hilite=trap

1 Answer

1
2.51K 2 Comments

Hi Miguel,

There are no filtering options and changes are low that we will add that as this functionality is going EOL.

Pieter Van Compernolle [SLC] [DevOps Enabler] Edited comment 16th September 2024
Miguel Barquet [SLC] [DevOps Enabler] commented

In our scenario, the customer wants to receive alarm updates in near real-time. If SNMP traps and TCP/IP sockets are not recommended options, which alternative functionality do you suggest we use to forward alarms to a third-party system? What advantages does this alternative offer in terms of security, reliability, flexibility, and ease of use compared to the other two options?
Pieter Van Compernolle [SLC] [DevOps Enabler] commented

SNMP traps are the built-in alternative.
I see other solutions going in the direction of a Connector that subscribes on (all?) the alarms and make them available in a way convenient for the use case. Checkout https://catalog.dataminer.services/ for a connector that matches your needs.
You are viewing 1 out of 1 answers, click here to view all answers.