Composite monitors

Table of contents

About composite monitors

Basic monitor types for the Alerting plugin are designed to define a single trigger type. For example, a per document monitor can trigger an alert based on a query’s match with documents, while a per bucket monitor can trigger an alert based on queries aimed at aggregated values in a data source. The composite monitor combines multiple monitors in a sequence to analyze a data source based on multiple criteria and then uses their individual alerts to generate a single chained alert. This allows you to derive more granular information about a data source, and it doesn’t require you to manually coordinate the scheduling of the separate monitors.

Composite monitors remove the limitations of basic monitors in the following ways:

  • Composite monitors give you the ability to create complex queries through a combination of triggers generated by multiple types of monitors.
  • They have the capacity to define a pipeline of rules and queries that are run as a single execution.
  • They deliver a single alert to users instead of multiple alerts from the individual monitors in their workflows.
  • They provide a more complete view of a given data source by running multiple monitors and multiple types of monitors in sequence, creating more focused results and reducing noise in the results.

Key terms

The key terms in the following table describe the basic concepts of composite monitors. For additional terms common to all types of monitors, see Key terms in the Alerting section.

TermDefinition
Composite monitorA composite monitor is a type of monitor that supports the execution of multiple monitors in a sequential workflow. It supports configuring triggers to create chained alerts.
Delegate monitorDelegate monitors are executed sequentially according to their order in a composite monitor’s definition. When a delegate monitor’s trigger conditions are met, it generates an audit alert. This audit alert then becomes a condition for the composite monitor’s trigger. The composite monitor supports per query, per bucket, and per document monitors as delegate monitors.
workflow IDThe workflow ID provides an identifier for the entire workflow of all delegate monitors. It is synonymous with a composite monitor’s monitor ID.
Chained alertChained alerts are generated from composite monitor triggers when delegate monitors generate audit alerts. The chained alert trigger condition supports the use of the logical operators AND, OR, and NOT so you can combine multiple functions into a single expression.
Audit alertDelegate monitors generate alerts in an audit state. Users are not notified about each individual audit alert and don’t need to acknowledge them. Audit alerts are used to evaluate chained alert trigger conditions in composite monitors.
ExecutionA single run of all delegate monitors in the sequence defined in the composite monitor’s configuration.

Basic workflow

You create composite monitors by combining individual monitors in a workflow that executes each monitor in a defined sequence. When individual audit alerts from the delegate monitors meet the trigger conditions for a composite monitor, the composite monitor generates its own chained alert. Consider the following sequence of events to understand how a simple composite monitor configured with two delegate monitors executes its workflow. In this example, the trigger condition for the composite monitor is met when the first monitor and the second monitor both generate an alert.

  1. The composite monitor starts the execution and delegates it to the first monitor. The trigger conditions for the first monitor are met and it generates an audit alert.
  2. The composite monitor then delegates the execution to the second monitor. The second monitor’s trigger conditions are also met and it generates its own audit alert.
  3. Because the composite monitor’s trigger conditions require that the first and second monitors both generate audit alerts, the composite monitor then triggers a chained alert.
  4. If notifications are configured in the composite monitor’s definition, users receive a notification about the chained alert. They do not, however, receive the individual audit alerts generated by the two delegate monitors.

In this simple example, the first monitor could be a per document monitor configured to analyze a data source using three different queries, while the second monitor could be a per bucket monitor that aggregates data by client IP. By combining the requirements of each delegate monitor, the composite monitor focuses the criteria that decide whether an alert is generated or not. This can improve the meaningfulness of the alert while removing extraneous alerts that provide no deterministic value.

Managing composite monitors with the API

You can manage composite monitors using the OpenSearch REST API or OpenSearch Dashboards. This section describes API functionality for composite monitors.

Create composite monitor

This API allows you to create a composite monitor.

  1. POST _plugins/_alerting/workflows

copy

Request fields

FieldTypeDescription
scheduleObjectThe schedule that determines how often the execution runs.
schedule.period.intervalNumeralAccepts a numerical value to set how often the execution runs.
schedule.period.unitObjectThe time unit of measure for the interval: SECONDS, MINUTES, HOURS, DAYS.
inputsObjectAccepts inputs to define the delegate monitors, which specify both the delegate monitors and their order in the execution’s sequence.
inputs.composite_input.sequence.delegatesObjectThe settings for the individual monitors that underlie the composite monitor.
inputs.composite_input.sequence.delegates.orderNumberDesignates the order in which the monitor runs in the execution.
inputs.composite_input.sequence.delegates.monitor_idStringThe unique identifier for the monitor.
enabled_timeNumberThe time at which the monitor was enabled. Expressed in epoch time.
enabledBooleanThe setting that determines whether the composite monitor is enabled or not. Setting it to true enables the composite monitor. Default is true.
workflow_typeStringSet to composite for composite monitor.
triggersObjectDetails for the individual alert triggers.
triggers.chained_alert_triggerObjectDetails for each individual alert trigger. Each monitor’s alert trigger will require settings for its configuration.
triggers.chained_alert_trigger.idStringThe unique identifier for the alert trigger.
triggers.chained_alert_trigger.nameStringThe name of the alert trigger.
triggers.chained_alert_trigger.severityNumberThe alert severity. 1 = highest; 2 = high; 3 = medium; 4 = low; 5 = lowest.
triggers.chained_alert_trigger.condition.scriptObjectThe script details that determine the conditions for triggering an alert.
triggers.chained_alert_trigger.condition.script.sourceStringThe Painless script that defines the conditions for triggering an alert.
triggers.chained_alert_trigger.condition.script.langStringEnter painless for the Painless scripting language.
actionsObjectProvides fields for configuring an alert notification.

Example request

  1. POST _plugins/_alerting/workflows
  2. {
  3.     "last_update_time": 1679468231835,
  4.     "owner": "alerting",
  5.     "type": "workflow",
  6.     "schedule": {
  7.         "period": {
  8.             "interval": 1,
  9.             "unit": "MINUTES"
  10.         }
  11.     },
  12.     "inputs": [{
  13.         "composite_input": {
  14.             "sequence": {
  15.                 "delegates": [{
  16.                         "order": 1,
  17.                         "monitor_id": "grsbCIcBvEHfkjWFeCqb"
  18.                     },
  19.                     {
  20.                         "order": 2,
  21.                         "monitor_id": "agasbCIcBvEHfkjWFeCqa"
  22.                     }
  23.                 ]
  24.             }
  25.         }
  26.     }],
  27.     "enabled_time": 1679468231835,
  28.     "enabled": true,
  29.     "workflow_type": "composite",
  30.     "name": "scale_up",
  31.     "triggers": [{
  32.             "chained_alert_trigger": {
  33.                 "id": "m1ANDm2",
  34.                 "name": "jnkjn",
  35.                 "severity": "1",
  36.                 "condition": {
  37.                     "script": {
  38.                         "source": "(monitor[id=grsbCIcBvEHfkjWFeCqb] && monitor[id=agasbCIcBvEHfkjWFeCqa])",
  39.                         "lang": "painless"
  40.                     }
  41.                 }
  42.             },
  43.             "actions": [{
  44.                 "name": "test-action",
  45.                 "destination_id": "ld7912sBlQ5JUWWFThoW",
  46.                 "message_template": {
  47.                     "source": "This is my message body."
  48.                 },
  49.                 "throttle_enabled": true,
  50.                 "throttle": {
  51.                     "value": 27,
  52.                     "unit": "MINUTES"
  53.                 },
  54.                 "subject_template": {
  55.                     "source": "TheSubject"
  56.                 }
  57.             }]
  58.         },
  59.         {
  60.             "chained_alert_trigger": {
  61.                 "id": "m1ORm2",
  62.                 "name": "jnkjn",
  63.                 "severity": "1",
  64.                 "condition": {
  65.                     "script": {
  66.                         "source": "(monitor[id=grsbCIcBvEHfkjWFeCqb] || monitor[id=agasbCIcBvEHfkjWFeCqa])",
  67.                         "lang": "painless"
  68.                     }
  69.                 }
  70.             }
  71.         }
  72.     ]
  73. }

copy

Using Painless scripting language to define chained alert trigger conditions

Composite monitor configurations employ the Painless scripting language to define the conditions for generating chained alerts. Conditions are applied for each execution of the composite monitor. You define the alert trigger conditions in the triggers.chained_alert_triggers.condition.script.source field of the request. Using Painless syntax, you can apply logic to links between monitors with the basic Boolean operators AND, OR, NOT, and precedence:

  • AND = &&
  • OR = ||
  • NOT = !
  • Precedence = ()

See the following examples to understand how each is used in the monitor definition.

  • Example 1

    monitor[id=1] && monitor[id=2]

    The following conditions for delegate monitors will trigger the composite monitor to produce a chained alert when both monitor #1 AND monitor #2 generate an alert.

  • Example 2

    monitor[id=1] || !monitor[id=2]

    The following conditions will trigger the composite monitor to produce a chained alert when either monitor #1 generates an alert OR monitor #2 does NOT generate an alert.

  • Example 3

    monitor[id=1] && (monitor[id=2] || monitor[id=3])

    The following conditions will trigger the composite monitor to produce a chained alert when monitor #1 generates an alert AND monitor #2 OR monitor #3 generates an alert.

The order of monitor IDs in the Painless script does not define the execution sequence for the monitors. The monitor execution sequence is defined in the inputs.composite_input.sequence.delegates.order field in the request.

Get Composite Monitor

This API retrieves information on the specified monitor.

  1. GET _plugins/_alerting/workflows/<workflow_id>

copy

Path parameters

FieldTypeDescription
workflow_idStringThe composite monitor’s workflow ID.

Update Composite Monitor

This API updates the composite monitor’s details. See Create Composite Monitor for descriptions of the request fields.

Example request

  1. PUT _plugins/_alerting/workflows/<workflow_id>
  2. {
  3.     "owner": "security_analytics",
  4.     "type": "workflow",
  5.     "schedule": {
  6.         "period": {
  7.         "interval": 1,
  8.         "unit": "MINUTES"
  9.         }
  10.     },
  11.     "inputs": [
  12.         {
  13.             "composite_input": {
  14.                 "sequence": {
  15.                     "delegates": [
  16.                         {
  17.                             "order": 1,
  18.                             "monitor_id": "grsbCIcBvEHfkjWFeCqb"
  19.                         },
  20.                         {
  21.                             "order": 2,
  22.                             "monitor_id": "agasbCIcBvEHfkjWFeCqa"
  23.                         }
  24.                     ]
  25.                 }
  26.             }
  27.         }
  28.     ],
  29.     "enabled_time": 1679468231835,
  30.     "enabled": true,
  31.     "workflow_type": "composite",
  32.     "name": "NTxdwApKbv"
  33. }

copy

Delete Composite Monitor

  1. DELETE _plugins/_alerting/workflows/<workflow_id>

copy

Execute Composite Monitor

This API begins the workflow execution for a composite monitor:

  1. POST /_plugins/_alerting/workflows/<workflow_id>/_execute

copy

Example response

  1. {
  2.     "execution_id": "I0GXeIgBYKBG2nHoiHCL_2023-06-01T20:18:48.511884_a9c1d055-9b70-49c2-b32a-716cff1f562e",
  3.     "workflow_name": "scale_up",
  4.     "workflow_id": "I0GXeIgBYKBG2nHoiHCL",
  5.     "trigger_results": {
  6.         "m1ANDm2": {
  7.             "name": "jnkjn",
  8.             "triggered": true,
  9.             "action_results": {},
  10.             "error": null
  11.         },
  12.         "m1ORm2": {
  13.             "name": "jnkjn",
  14.             "triggered": true,
  15.             "action_results": {},
  16.             "error": null
  17.         }
  18.     },
  19.     "monitor_run_results": [{
  20.             "monitor_name": "test triggers",
  21.             "period_start": 1685650668501,
  22.             "period_end": 1685650728501,
  23.             "error": null,
  24.             "input_results": {
  25.                 "results": [{
  26.                     "bhjh": [
  27.                         "OkGceIgBYKBG2nHoyHAn|test1",
  28.                         "O0GceIgBYKBG2nHozHCW|test1"
  29.                     ],
  30.                     "nkjkj": [
  31.                         "OkGceIgBYKBG2nHoyHAn|test1",
  32.                         "O0GceIgBYKBG2nHozHCW|test1"
  33.                     ],
  34.                     "jknkjn": [
  35.                         "OkGceIgBYKBG2nHoyHAn|test1",
  36.                         "O0GceIgBYKBG2nHozHCW|test1"
  37.                     ]
  38.                 }],
  39.                 "error": null
  40.             },
  41.             "trigger_results": {
  42.                 "NC3Dd4cBCDCIfBYtViLI": {
  43.                     "name": "njkkj",
  44.                     "triggeredDocs": [
  45.                         "OkGceIgBYKBG2nHoyHAn|test1",
  46.                         "O0GceIgBYKBG2nHozHCW|test1"
  47.                     ],
  48.                     "action_results": {},
  49.                     "error": null
  50.                 }
  51.             }
  52.         },
  53.         {
  54.             "monitor_name": "test triggers 2",
  55.             "period_start": 1685650668501,
  56.             "period_end": 1685650728501,
  57.             "error": null,
  58.             "input_results": {
  59.                 "results": [{
  60.                     "bhjh": [
  61.                         "PEGceIgBYKBG2nHo1HCw|test",
  62.                         "PUGceIgBYKBG2nHo3HA8|test"
  63.                     ],
  64.                     "nkjkj": [
  65.                         "PEGceIgBYKBG2nHo1HCw|test",
  66.                         "PUGceIgBYKBG2nHo3HA8|test"
  67.                     ],
  68.                     "jknkjn": [
  69.                         "PEGceIgBYKBG2nHo1HCw|test",
  70.                         "PUGceIgBYKBG2nHo3HA8|test"
  71.                     ]
  72.                 }],
  73.                 "error": null
  74.             },
  75.             "trigger_results": {
  76.                 "NC3Dd4cBCDCIfBYtViLI": {
  77.                     "name": "njkkj",
  78.                     "triggeredDocs": [
  79.                         "PEGceIgBYKBG2nHo1HCw|test",
  80.                         "PUGceIgBYKBG2nHo3HA8|test"
  81.                     ],
  82.                     "action_results": {},
  83.                     "error": null
  84.                 }
  85.             }
  86.         }
  87.     ],
  88.     "execution_start_time": "2023-06-01T20:18:48.511874Z",
  89.     "execution_end_time": "2023-06-01T20:18:53.682405Z",
  90.     "error": null
  91. }

Get chained alerts

This API returns an array of chained alerts generated in composite monitor workflows:

  1. GET /_plugins/_alerting/workflows/alerts?workflowIds=<workflow_ids>&getAssociatedAlerts=true

Query parameters

FieldTypeRequiredDescription
workflowIdsArrayNoWhen this parameter is used, it returns alerts created by the specified workflows.
getAssociatedAlertsBooleanNoWhen true, the response returns audit alerts that the composite monitor used to create a chained alert. Default is false.

Example response

  1. {
  2.     "alerts": [
  3.         {
  4.             "id": "PbQoZokBfd2ci_FqMGi6",
  5.             "version": 1,
  6.             "monitor_id": "",
  7.             "workflow_id": "G7QoZokBfd2ci_FqD2iZ",
  8.             "workflow_name": "scale_up",
  9.             "associated_alert_ids": [
  10.                 "4e8256c5-529a-484c-bf7b-d3980c03e9a4",
  11.                 "513a8cb3-44bc-4eee-8aac-131be10b399e"
  12.             ],
  13.             "schema_version": -1,
  14.             "monitor_version": -1,
  15.             "monitor_name": "",
  16.             "execution_id": "G7QoZokBfd2ci_FqD2iZ_2023-07-17T23:20:55.244970_edd977d2-c02b-4cbe-8a79-2aa7991c4191",
  17.             "trigger_id": "m1ANDm2",
  18.             "trigger_name": "jnkjn",
  19.             "finding_ids": [],
  20.             "related_doc_ids": [],
  21.             "state": "ACTIVE",
  22.             "error_message": null,
  23.             "alert_history": [],
  24.             "severity": "1",
  25.             "action_execution_results": [],
  26.             "start_time": 1689636057269,
  27.             "last_notification_time": 1689636057270,
  28.             "end_time": null,
  29.             "acknowledged_time": null
  30.         },
  31.         {
  32.             "id": "PrQoZokBfd2ci_FqMGj8",
  33.             "version": 1,
  34.             "monitor_id": "",
  35.             "workflow_id": "G7QoZokBfd2ci_FqD2iZ",
  36.             "workflow_name": "scale_up",
  37.             "associated_alert_ids": [
  38.                 "4e8256c5-529a-484c-bf7b-d3980c03e9a4",
  39.                 "513a8cb3-44bc-4eee-8aac-131be10b399e"
  40.             ],
  41.             "schema_version": -1,
  42.             "monitor_version": -1,
  43.             "monitor_name": "",
  44.             "execution_id": "G7QoZokBfd2ci_FqD2iZ_2023-07-17T23:20:55.244970_edd977d2-c02b-4cbe-8a79-2aa7991c4191",
  45.             "trigger_id": "m1ORm2",
  46.             "trigger_name": "jnkjn",
  47.             "finding_ids": [],
  48.             "related_doc_ids": [],
  49.             "state": "ACTIVE",
  50.             "error_message": null,
  51.             "alert_history": [],
  52.             "severity": "1",
  53.             "action_execution_results": [],
  54.             "start_time": 1689636057340,
  55.             "last_notification_time": 1689636057340,
  56.             "end_time": null,
  57.             "acknowledged_time": null
  58.         }
  59.     ],
  60.     "associatedAlerts": [
  61.         {
  62.             "id": "4e8256c5-529a-484c-bf7b-d3980c03e9a4",
  63.             "version": -1,
  64.             "monitor_id": "DrQoZokBfd2ci_FqCWh8",
  65.             "workflow_id": "G7QoZokBfd2ci_FqD2iZ",
  66.             "workflow_name": "",
  67.             "associated_alert_ids": [],
  68.             "schema_version": 5,
  69.             "monitor_version": 1,
  70.             "monitor_name": "test triggers",
  71.             "execution_id": "G7QoZokBfd2ci_FqD2iZ_2023-07-17T23:20:55.244970_edd977d2-c02b-4cbe-8a79-2aa7991c4191",
  72.             "trigger_id": "NC3Dd4cBCDCIfBYtViLI",
  73.             "trigger_name": "njkkj",
  74.             "finding_ids": [
  75.                 "277afca7-d5aa-46ed-8023-5449ece65d36"
  76.             ],
  77.             "related_doc_ids": [
  78.                 "H7QoZokBfd2ci_FqFmii|test1"
  79.             ],
  80.             "state": "AUDIT",
  81.             "error_message": null,
  82.             "alert_history": [],
  83.             "severity": "1",
  84.             "action_execution_results": [],
  85.             "start_time": 1689636056410,
  86.             "last_notification_time": 1689636056410,
  87.             "end_time": null,
  88.             "acknowledged_time": null
  89.         },
  90.         {
  91.             "id": "513a8cb3-44bc-4eee-8aac-131be10b399e",
  92.             "version": -1,
  93.             "monitor_id": "EbQoZokBfd2ci_FqCmiR",
  94.             "workflow_id": "G7QoZokBfd2ci_FqD2iZ",
  95.             "workflow_name": "",
  96.             "associated_alert_ids": [],
  97.             "schema_version": 5,
  98.             "monitor_version": 1,
  99.             "monitor_name": "test triggers 2",
  100.             "execution_id": "G7QoZokBfd2ci_FqD2iZ_2023-07-17T23:20:55.244970_edd977d2-c02b-4cbe-8a79-2aa7991c4191",
  101.             "trigger_id": "NC3Dd4cBCDCIfBYtViLI",
  102.             "trigger_name": "njkkj",
  103.             "finding_ids": [
  104.                 "6d185585-a077-4dde-8e43-b4c01b9f3102"
  105.             ],
  106.             "related_doc_ids": [
  107.                 "ILQoZokBfd2ci_FqGmhb|test"
  108.             ],
  109.             "state": "AUDIT",
  110.             "error_message": null,
  111.             "alert_history": [],
  112.             "severity": "1",
  113.             "action_execution_results": [],
  114.             "start_time": 1689636056943,
  115.             "last_notification_time": 1689636056943,
  116.             "end_time": null,
  117.             "acknowledged_time": null
  118.         }
  119.     ],
  120.     "totalAlerts": 2
  121. }

Request fields

FieldTypeDescription
alertsArrayA list of chained alerts generated by the composite monitor.
associatedAlertsArrayA list of audit alerts generated by the delegate monitors.

Acknowledge chained alerts

After getting your alerts, you can acknowledge multiple active alerts in one call. If the alert is already in an ERROR, COMPLETED, or ACKNOWLEDGED state, it appears in the failed array.

  1. POST _plugins/_alerting/workflows/<workflow_id>/_acknowledge/alerts
  2. {
  3.     "alerts": ["eQURa3gBKo1jAh6qUo49"]
  4. }

copy

Request fields

FieldTypeDescription
alertsArrayA list of alerts by ID. The results include alerts that are acknowledged by the system as well as alerts not recognized by the system.

Example response

  1. {
  2.     "success": [
  3.     "eQURa3gBKo1jAh6qUo49"
  4.     ],
  5.     "failed": []
  6. }

Creating composite monitors in OpenSearch Dashboards

Begin by navigating to the Create monitor page in OpenSearch Dashboards: Alerting > Monitors and select Create monitor. Give the monitor a name and then select Composite monitor as the monitor type. Steps for creating a composite monitor workflow and trigger conditions vary depending on whether you use the Visual editor or the Extraction query editor. The first provides basic UI selectors for defining the composite monitor, while the second allows you to build the workflow and trigger conditions using a script. After deciding which method to use, refer to the corresponding section.

Visual editor

To use the visual editor for defining a workflow and trigger conditions, select the Visual editor radio button in the Monitor defining method section. This is shown in the following image.

Selecting the Visual editor

To finish creating a composite monitor in the visual editor, follow these steps:

  1. In the Frequency dropdown list, select either By interval, Daily, Weekly, Monthly, or Custom cron expression:
    • By interval — Allows you to run the schedule repeatedly based on the number of minutes, hours, or days you specify.
    • Daily — Specify a time of day and a time zone.
    • Weekly — Specify a day of the week, a time of day, and a time zone.
    • Monthly — Specify a day of the month, a time of day, and a time zone.
    • Custom cron expression — Create a custom cron expression for the schedule. Use the cron expressions link for help with creating these expressions, or see the Cron expression reference.

  2. In the Delegate monitors section, enter the individual monitors you want to include in the workflow by selecting them in the dropdown lists. In the Visual editor, the order in which you select the monitors determines their order in the workflow.

    Select Add another monitor to add another dropdown list. A minimum of two delegate monitors are required, and a maximum of 10 are allowed in total. Keep in mind that composite monitors support per query, per bucket, and per document monitors as delegate monitors.

    Beside each dropdown list, you can select the view monitor icon (view monitor icon) to open the monitor’s details window and review information about it.

  3. Define a trigger or triggers for the composite monitor. In the Triggers section, select Add trigger. Add a trigger name, then define the trigger conditions.

    • Use the Select delegate monitor label to open the pop-up window shown in the following image.

    This pop-up window shows options for selecting a delegate monitor and trigger condition operator

    • Use the Select delegate monitor dropdown list to select a delegate monitor from those defined in the previous step. For the first delegate monitor, you can select NOT as the operator if you prefer. After the monitor is populated in the field, you can use the trash can icon (trash can icon) to the right of the list to remove the monitor if needed.
    • Select the plus sign (plus sign) to the right of the first monitor to select a second delegate monitor. After selecting a second monitor, select one of the operators AND, OR, AND NOT, or OR NOT to apply the condition between the two monitors. After the operator is applied, you can select the operator to open the pop-up window again and change the selection.
    • Select the severity level for the alert. The options include 1 (Highest), 2 (High), 3 (Medium), 4 (Low), and 5 (Lowest).

    • In the Notifications section, select a notification channel from the dropdown list. If no channels exist, select the Manage channels label to the right of the dropdown list to set up a notification channel. For more information about notifications, see the Notifications documentation. You can also select Add notification to specify additional notifications for the alert trigger.

      Notifications are optional for all monitor types.

    • To define an additional trigger, select Add another trigger. You can have a maximum of of 10 triggers in total. Select Remove trigger to the right of the screen to remove a trigger.

  4. After completing the monitor workflow and defining triggers, select Create in the lower-right corner of the screen. The composite monitor is created, and the monitor’s details window opens.

Extraction query editor

To use the extraction query editor for defining a workflow and triggers, select the Extraction query editor radio button in the Monitor defining method section. This is shown in the following image.

Selecting the Extraction query editor

The extraction query editor follows the same general steps as the visual editor, but it allows you to build the composite monitor workflow and alert triggers using extractions from the API query. This provides you with the ability to create more advanced configurations not supported by the visual editor. The following sections provide examples of content for each of these two fields. All other steps for composite monitor creation are the same as in those for the visual editor.

  • Define workflow

    In the Define workflow field, enter a sequence that defines the delegate monitors and their order in the workflow. The following example shows the delegate monitors that are included in the workflow, along with their order in the sequence:

    1. {
    2.     "sequence": {
    3.         "delegates": [
    4.             {
    5.                 "order": 1,
    6.                 "monitor_id": "0TgBZokB2ZtsLaRvXz70"
    7.             },
    8.             {
    9.                 "order": 2,
    10.                 "monitor_id": "8jgBZokB2ZtsLaRv6z4N"
    11.             }
    12.         ]
    13.     }
    14. }

    All delegate monitors included in the workflow require a monitor_id and a value for order.

  • Trigger condition

    In the Trigger condition field, enter the monitors and the operators that will be used to define the conditions between them. This field requires that trigger conditions be formatted in Painless scripting language. To see how these scripts are formed for trigger conditions, see Using Painless scripting to define chained alert trigger conditions.

    The following example shows a trigger condition requiring the first monitor OR the second monitor to generate an audit alert before the composite monitor can generate a chained alert:

    1. (monitor[id=8d36S4kB0DWOHH7wpkET] || monitor[id=4t36S4kB0DWOHH7wL0Hk])

Viewing monitor details

After a composite monitor is created, it appears in the list of monitors on the Monitors tab. The Type column indicates the type of monitor, including the composite monitor type. The Associations with composite monitors column provides a count of how many composite monitors a basic monitor is used in as a delegate monitor. Select a monitor in the Monitor name column to open its details window.

For composite monitors, The Alerts section of the details window includes the Actions column, which includes the view details icon (view monitor icon). The following image shows the Actions column as the last column to the right.

Alerts section of the monitor details window

Select this icon to open the Alert details window. This window shows you all of the audit alerts that were part of the execution that generated the chained alert and includes the delegate monitor that generated the audit alert. Select the X in the upper-right corner of the window to close Alert details.

After returning to the Alerts section of the monitor’s details window, you can select the check box to the left of the Alert start time to highlight the alert. After the alert is highlighted, you can select Acknowledge in the upper-right portion of this section. The alert is acknowledged and the status in the State column changes from Active to Acknowledged.