This documentation supports an earlier version of BMC Helix Operations Management.

To view the documentation for the latest version, select 23.1 from the Product version picker.

Information sharing between enrichment policies with global variables

Global variables are structured records that maintain data values across all phases of event processing. You can use these variables in event enrichment policies for sharing information between events during event processing; any other type of variable (local) has a scope limited to the current policy.


Sarah is an administrator at Apex Global. Her company receives third-party events from Nagios and want to use the entity details in the event to enrich multiple events through enrichment policies. To achieve this goal, she can create a global variable to store the entity details and use it between event enrichment policies for enriching events.

Usage of global variables

You can use global variables in the following scenarios to:

  • Filter event slots by using event operators with global variables. For more information about event operators, see Slot data types.
  • Build conditions for processing events.
  • Point to static text, event data (values of event slots), results of mathematical functions, and values of previously-defined variables in enrichment policies.
  • Specify global variables in the external source file for the match and enrichment values for enriching events by using dynamic enrichment policies. For more information, see Specifying global variables in an external file.
  • Filter events by using the event selection criteria. For more information, see Creating and enabling event policies.
  • Specify notification settings while creating a notification policy. For more information, see Event-based notifications for alerting users.
  • Set global variable attribute values in event enrichment policies. For more information, see Actions for advanced and time-based enrichment.
  • Specify global variables in Enrich, Function, If, and Variable action settings on the policy workflow.

You can use APIs to manage global variables and event enrichment policies to fetch the variable values. For more information, see Managing global variables with REST APIs,

From the GUI, you can update global variables but not create them. For updating global variables from the GUI, see Actions for advanced and time-based enrichment.

Global variables are addressed by name, so you must know the name of the global variable to use it. Global variable names do not contain a space and are prefixed with $GV. A global variable consists of attributes that can have only the String data type. You cannot nest global variables. Use the following syntax to refer to an attribute listed in a global variable:


Examples for global variables

Refer the following global variable examples:

Example 1


Here, entity_name, entity_location, and entity_status are attributes of the $GV.entity_details global variable.

Example 2

$GV.nagios_contact.contact_name=John Doe

Example 3 (Global variables used in the external source file for dynamic enrichment policies) 


The following column mappings are in this file:

Column 1 corresponds to the Hostname match slot
Column 2 corresponds to the Message match slot
Column 3 corresponds to the Owner enrichment slot

Was this page helpful? Yes No Submitting... Thank you


  1. Mukta Kirloskar

    Hi Tim,

    I am moving this comment to the master space and removing it from here.


    May 20, 2022 03:45