Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..
768 views

Use Wildcard in Related CI Node Hint?

Jump to solution

Hi, 

We are building some integrations into OMi from some external monitors.

We are forwarding events easily using the external WebService API.

When we send events, sometimes we do not know the full primary_dns_name of the target node as it is defined in OMI.

This means that if I set the RelatedCI hint to:

@@webserver001

it will not correlate to the CI with DNS name of

@@webserver001.some.fully.qualified.com

The "name" of the CI is just the short name, but I am not sure how the back-end code queries against RTSM.

So, we end up with alerts without a Node related to them, which is pretty useless for KPIs.

D

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

The online help at:

http://docs.software.hpe.com/OMi/10.61/Content/OMi/AdminGuide/om_auto_event_handling_CI_resolution.htm

explains what CI attributes are used to resolve an event to a node CI:

The node reference is retrieved from the RTSM as follows:
a.Fully qualified domain name (primary_dnsname)
b.IP address taken from the related ip_address in the RTSM:
* ip_address.authoritative_dns_name attribute
* ip_address.ip_address attribute
c.OM core ID. A name attribute taken from the related hp_operationsagent CI in the RTSM.

So, if you have the IP address, that could work.  Or if you can figure out the domain name of the host, then you could append it - either in your REST call (preferred) or via EPI Groovy script (search for example scripts at https://marketplace.saas.hpe.com/itom/search?q=EPI+Script).  If you have a small number of possible different domain names (and assuming the hostname doesn't get duplicated across domains), you could have teh EPI Groovy script set the Related CI Hint to include multiple choices:

hostname|hostname.fqdn1|hostname.fqdn2|hostname.fqdn3

OMi tries to resolve hostname to a CI. If that fails it tries hostname.fqdn1.  If that fails it tries hostname.fqdn2, and so on.

CP.

View solution in original post

2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

The online help at:

http://docs.software.hpe.com/OMi/10.61/Content/OMi/AdminGuide/om_auto_event_handling_CI_resolution.htm

explains what CI attributes are used to resolve an event to a node CI:

The node reference is retrieved from the RTSM as follows:
a.Fully qualified domain name (primary_dnsname)
b.IP address taken from the related ip_address in the RTSM:
* ip_address.authoritative_dns_name attribute
* ip_address.ip_address attribute
c.OM core ID. A name attribute taken from the related hp_operationsagent CI in the RTSM.

So, if you have the IP address, that could work.  Or if you can figure out the domain name of the host, then you could append it - either in your REST call (preferred) or via EPI Groovy script (search for example scripts at https://marketplace.saas.hpe.com/itom/search?q=EPI+Script).  If you have a small number of possible different domain names (and assuming the hostname doesn't get duplicated across domains), you could have teh EPI Groovy script set the Related CI Hint to include multiple choices:

hostname|hostname.fqdn1|hostname.fqdn2|hostname.fqdn3

OMi tries to resolve hostname to a CI. If that fails it tries hostname.fqdn1.  If that fails it tries hostname.fqdn2, and so on.

CP.

View solution in original post

Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Thanks. In our case it looks like using the "OR" syntax to try multiple domains will work.

In our case we know most of the domain possibilities, so we can just send all possible variations.

 

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.