Spectrumgtw events to NAS and nas Alarm_enrichment.
Understand that the Spectrumgtw probes send the the events to EMS and we could use EMS Event rules to enrich the events, but we have a requirement where we want to forward the spectrum events to NAS and NAS Alarm_enrichment, so that i could use the alarm_enrichment to query a database and then update the custom fields with information from the database.
I have try using the route from alarm_routing service, but not able to get the alarm_enrichment done.
Any one had any luck enrich the spectrum events by using nas alarm_enrichment.
Unfortunately the spectrumgtw probe doesn't use the message bus for the alarm ingestion from spectrum and so you won't be able to use Alarm Enrichment/NAS
So is there anyway we could enrich the events? I understand for EMS events, we could use the EventRule or AlarmRule to define some enrichment, but so far no luck on it.
Does the Spectrum Events goes through the EventRule or does it goes to alarmRule?
And if it spectrumgtw doesn't use the message bus, how does the event flow happens?
The spectrumgtw probe synchronizes Spectrum alarms through the ems alarm API. See the Integration Architecture Wiki page for details.
Any alarm enrichment of the Spectrum alarms must be done through the ems probe. You would do this by defining ems Alarm Rules, but this is not a trivial task since there are no GUI interfaces to help with the generation of the appropriate XML rule catalogs.
For specific information on generating ems rules see the following ems Wiki pages:
Creating Event and Alarm Rules with the XML Rule Catalogs
ems Rule Method Reference
ems Event Handling and EMMessage Structure
For some sample use cases see the ems Use Rule Cases Wiki page.
Believe or not, ems probe has a built-in rule dedicated to spectrum gateway.
yes Yu, there is a dedicated built in rule for Spectrum Gateway, that why i was bit confuse where the enrichment has to be done.
I understand that the event goes through the eventrule and then to Alarm rule, so for Spectrumgtw does it goes to alarmrule directly? If yes, then we have to configure the enrichment on the alarmrule.xml itself.
Thank you for response.
Would you please describe what types of enrichment you would like on Spectrum alarms ?
In the Spectrum events, we want to add some additional details on the Alarms, i.e on the Custom_1, Custom_2 field. this would be an hard-coded value.
so that when an spectrum Alarm is received in UIM Alarm Console, the Custom_1, Custom_2 should have some values on it. eg Custom_1 = Network etc....
Thank you for input. Do you want to add fixed value of user tag for all spectrum alarms ?
Was able to resolve this with CA Support assistance. the changes was done on the actionrule.xml file.
here is sample....
Map<String, Object> updates = new HashMap<>()
Map<String, Object> removes = null
getAlarmService().updateProperties(getAlarmContext(), updates, removes)
Thank you for sharing, it is very valuable share.
So for those user who want event enrichment for Spectrum events to UIM and Auto Assigned to a user..... we are using the below Actionrule.xml under custom folder. Hope Fellow user would find it helpful for this event Enrichment.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><eventRules xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <items> <item id="d5aa0a48-8117-400d-9c9c-0275c743918f" name="Auto-assign alarms" xsi:type="ActionManagerRule"> <enabled>true</enabled> <eventTypes> <eventType>com.ca.uim.ems.alarm.created</eventType> </eventTypes> <alarmFilter> <conditions> <condition propertyName="applicationId" operator="Equals" xsi:type="StringFilterCondition"> <value>SPECTRUM</value> </condition> </conditions> </alarmFilter> <actions> <action xsi:type="GroovyAction"> <script> <![CDATA[ Map<String, Object> updates = new HashMap<>() updates.put("custom_1", "Network") Map<String, Object> removes = null getAlarmService().updateProperties(getAlarmContext(), updates, removes) ]]> </script> </action>
<action xsi:type="AssignAction"> <assignedBy>administrator</assignedBy> <assignedTo>administrator</assignedTo> </action> </actions> </item> </items></eventRules>
Credit to CA support for this