Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
317 views

Node Down Event with Device Custom Attributes not passing values

Jump to solution

Hello, 

As per HPE NNM 10.30 documentation that custom attributes values can be passed to Incidents message. Link

Use the following syntax to specify a Custom Attribute for a Node: valueOfNodeCa(<CA_Name>)

For example: ${valueOfNodeCa(Location)} = USA

have Configured Custom attributes for device as below Device-Custom-attribute.PNG

Here is Node Down Incident message configuration:

Node $snn is Down #IP address: $mga ,
Located: $slc,
Customer:${valueOfNodeCa(CUSTOMER_NAME)},
Division:${valueOfNodeCa(Division)},
Location:${valueOfNodeCa(Location)},
Media_Type:${valueOfNodeCa(Media_Type)},
UPE_Name:${valueOfNodeCa(UPE_Name)}.

 

Here what i got when testing this 

Node Customer-Lab-Switch-3 is Down #IP address: 172.16.16.101 ,
Located: Customer-Lab-Switch-3-Rack01-index05,
Customer:${valueOfNodeCa(CUSTOMER_NAME)},
Division:${valueOfNodeCa(Division)},
Location:${valueOfNodeCa(Location)},
Media_Type:${valueOfNodeCa(Media_Type)},
UPE_Name:${valueOfNodeCa(UPE_Name)}.

 

Is there any syntax error here?

Regards
Mostafa Hassan
--------------------------------------
If my post helped you, kindly click the 'Kudos' button.
Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Node Down Event with Device Custom Attributes not passing values

Jump to solution

Hi Mostafa,

  The use of ${valueOfNodeCa{label)}  is documented for use in filters with respect to features like custom correlation.  It is not documented for use with incident message formats.   The way to get a Node Custom Attribute into an incident is to "Enrich" the incident and under the Custom Attribute tab configure the Node or Interface CA name, the Custom Incident Attribute name  ( e.g.  cia.owner )   and then in the event message you can use it as   $cia.owner.    You will also see the enriched CIAs in the incidents Custom Attribute tab in the analysis pane if the enrichment has been successful.

  I hope this explains things

  All the best

Dave Y

MicroFocus Support
Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of MicroFocus
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

2 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Node Down Event with Device Custom Attributes not passing values

Jump to solution

Hi Mostafa,

  The use of ${valueOfNodeCa{label)}  is documented for use in filters with respect to features like custom correlation.  It is not documented for use with incident message formats.   The way to get a Node Custom Attribute into an incident is to "Enrich" the incident and under the Custom Attribute tab configure the Node or Interface CA name, the Custom Incident Attribute name  ( e.g.  cia.owner )   and then in the event message you can use it as   $cia.owner.    You will also see the enriched CIAs in the incidents Custom Attribute tab in the analysis pane if the enrichment has been successful.

  I hope this explains things

  All the best

Dave Y

MicroFocus Support
Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of MicroFocus
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

View solution in original post

Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Node Down Event with Device Custom Attributes not passing values

Jump to solution

@Dave Young , thanks for your explination , i might got confused in that part,

i tested what you have mentioned and working totally fine as expected.

Regards
Mostafa Hassan
--------------------------------------
If my post helped you, kindly click the 'Kudos' button.
0 Likes
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.