Enable the ability to pass device attributes as CMA's (Custom Message Attributes)

Idea ID 1674206

Enable the ability to pass device attributes as CMA's (Custom Message Attributes)

Enhancement:

Enable the ability of NNMi to pass node/device CMA's (custom attributes) defined in NNMi for that node/device to Ops Bridge Connector and/or Operations Agent

Example:

If an alert is generated for a device it would be nice to see the custom attributes of the device which generated the alerts. (such as site location, country, region, etc)

Passing an assignment group for ticketing or alerting based on node/device/or interface
instead of being only able to pass nnm.securityGroup

Business Purpose:

Enables better customization capability of event text and event handling within Agent Policy, BSMC/OBC, and within OMi/OBM

Tags (1)
7 Comments
Micro Focus Expert
Micro Focus Expert
Moved to waiting for votes.
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
Cadet 3rd Class
Cadet 3rd Class

this will be very helpful for separate events thats comes from NNMi to OMi.

 

Thanks.

Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

Very useful idea

Captain
Captain

I'd like to add that many others would find it valuable to get 
1.) CMA's
2.) Security Group Names
3.) NNM Event Incident ID's

for cross launching or passing that info from NNMi to OBM for additional event data handling such as noting the NNM URL with the event ID to directly launch to the incident in NNMi from external ITSM or paging systems based on OBM event.

-Brandon

Captain
Captain

@AkashDeep Status Update on this? 
Especially now with the Agent Based integration this should be more feasible vs. the BSMC/OBC integration that was present in 2018 or earlier when this request was first submitted.

-Brandon

Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

We had a fix for NNMi(CA)->NNMi(CIA)->OBM(CMA) case is SD02682297 because there followed a trailing comma for last CMA in CA->CIA->CMA chain.

1. We update CA:s in NNMi 2020.05 from uCMDB adaptor (own created adaptor that sets different CA from node properties but it is quite similar to the default one except that ours takes more props/CA:s than UCMDB-ID)

2. In NNMi the wanted CA:s is varbound to CIA:s through Enrichment (management event configuration in NNMi)

3. We split CIA:s to CMA:s in Agent (ovtrapi)

[root@nnmiserver ~]# /opt/OV/bin/ovconfget eaagt.integration.nnm
OPC_SPLIT_NNM_CUSTOM_ATTR=TRUE
OPC_SPLIT_NNM_CUSTOM_ATTR_MAX=20

4. All CA:s bound to CIA:s exists as CMA:s and after the fix there are no trailing commas.

You could use Enrichment (management event configuration in NNMi) to update CIA:s also with NNMi-groups and more so feature is there. 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.