Fame Glow Feed

Premium fame highlights with sleek curation.

general

Slot facets - Documentation for BMC Helix Operations Management 21.3

Writer Michael Hansen

Indicates that the slot value holds the equivalent slot name that is used to look up topology information in BMC Helix Dynamic Service Modeling. While creating custom slots, you need to specify this facet for only those slots that are meant to be used looking up topology information.

Some out-of-the-box slots are already defined with this facet type. For example, source_hostname and source_address under the base Event class. The value of these slots is used for retrieving the service IDs and node IDs from BMC Helix Dynamic Service Modeling. These slots are used for displaying service models in BMC Helix AIOps. For more information, see _node_id, _service_id, and _node_service_mapping slots under the base Event class.

If no facet slots are defined for a custom event class, the out-of-the-box facet slots are used for looking up the topology information.

Important

You cannot mark slots, which have the STRING_LIST or INTEGER_LIST data type with this facet to lookup topology information.

Example of a class definition with the topology_lookup facet:

{ "name": "NAGIOS_EV", "attributes": [ { "name": "custom_slot_1", "dataType": "STRING", "allFacet": [ { "name": "topology_lookup", "value": "custom_slot_1_field_in_SmartGraph" } ] }, { "name": "custom_slot_2", "dataType": "INTEGER" } ]
}