Generated Agents and Modules

One agent per region

When Create agent per impacted region is enabled, the name follows this format:

<Agent prefix><Impacted region>

Example:

Azure Service Health West Europe

Single agent

When the option is disabled, every module is assigned to Target agent. The region is included in each module name to prevent collisions:

West Europe Events count
Spain Central Events count

When Module prefix is also configured, it appears before the region.

Generated modules

Every module is assigned to the Azure Service Health Events module group.

Module	Pandora module type	Data
`Connection`	`generic_proc`	`1` when the region appears in the current query and `0` after it disappears.
`Events count`	`generic_data`	Number of unique events affecting the region.
`New events count`	`generic_data`	Number of new or updated events since the previous execution.
`Active events count`	`generic_data`	Events whose regional or general status is `Active`.
`Critical events count`	`generic_data`	Events with the `Critical` level.
`Warning events count`	`generic_data`	Events with the `Warning` level.
`Events`	`generic_data_string`	Details of every matching event.
`New events`	`generic_data_string`	Details of new or updated events; returns the integer `0` when no updates are available.

Detail modules include the title, tracking ID, subscription, status, level, type, subtype, timestamps, service, region and summary whenever available. If the text exceeds the configured limit, it is truncated and the module indicates that the complete content is available in the JSONL log.