---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Alert insight properties

# Alert insight properties {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Alert Insight Properties

This guide details the configuration properties for Alert Insight within ServiceNow, essential for managing alert data effectively.
The required role to access these properties isevtmgmtadmin.
Show full answer Show less  

## Key Features

* **Time Frame Properties:**
  * **evtmgmt.alertinsightalerthistorymin:** Sets the time frame (in minutes) for retrieving repeated and similar alerts, defaulting to 30 days.
  * **evtmgmt.alertinsightclosedalertwindow:** Defines the time frame for retrieving closed alerts after the last update, defaulting to 3 days.
* **Similarity Properties:**
  * **evtmgmt.alertinsightalertsameasfilter:** Specifies fields to determine alert similarity, with default fields including source, type, resource, and metric name.
* **Related CIs Configuration:**
  * **evtmgmt.alertinsightrelatedcistopologylevels:** Sets the depth of related CI relationships, defaulting to 3 levels.
  * **evtmgmt.relatedcisgetallrelationtypes:** Controls retrieval of relation types, defaulting to false.
  * **evtmgmt.relatedcisusecontainmentrules:** Utilizes metadata containment rules, defaulting to true.
  * **evtmgmt.relatedcisusehostingrules:** Employs metadata hosting rules, defaulting to true.
  * **evtmgmt.relatedcisvalidaterelationrules:** Validates CI relations according to metadata rules, defaulting to true.
* **Score Mapping Properties:**
  * Properties such as **evtmgmt.alertinsightgroupmapping** and **evtmgmt.alertinsightlevelXmapping** define scores for relationships based on their depth, aiding in determining relevance.

## Key Outcomes

By adjusting these properties, users can customize alert insights, enhancing the relevance of related alerts and configuration items displayed. This leads to improved decision-making and prioritization of responses to alerts based on the configured metrics and relationships.  
Use these properties to configure alert insight.
The role required: evt_mgmt_admin The following alert_insight properties are under sys_properties.
{#configure-alert-insight-properties__table_zm2_n3c_y2b__entry__2}

| Property | Usage |
|-|-|
| Time Frame ||
| evt_mgmt.alert_insight_alert_history_min | Set the time frame (in minutes) to retrieve repeated and similar alert data. Default <kbd class="ph userinput">43200</kbd> (30 days) Note: Alerts are retrieved regardless of their state (open / reopen / flapping / closed). |
| evt_mgmt.alert_insight_closed_alert_window | Set the time frame (in minutes) to retrieve alerts that were already closed. It is the time after the alert last updated date. Default: <kbd class="ph userinput">4320</kbd> (3 days) |
| Similarity ||
| evt_mgmt.alert_insight_alert_same_as_filter | This property is a comma-separated string that defines which of the alert fields is used to consider alerts to be similar. Default: <kbd class="ph userinput">source,type,resource,metric_name</kbd> |
| Related CIs ||
| evt_mgmt.alert_insight_related_cis_topology_levels The relationship types are: * CMDB based (metadata rules and suggested relations) * Within application services * Within Alert groups {#configure-alert-insight-properties__ul_mnm_jjc_y2b} | For 'Within application service' relationship type, this property sets the depth or the maximum level of relationship of retrieved CIs. Default: <kbd class="ph userinput">3</kbd> |
| Score ||
| evt_mgmt.alert_insight_group_mapping | This property sets the score for within alert group relations. Default: <kbd class="ph userinput">2</kbd> |
| evt_mgmt.alert_insight_level_1_mapping | This property sets the score for level 1 relationship. Default: <kbd class="ph userinput">3</kbd> |
| evt_mgmt.alert_insight_level_2_mapping | This property sets the score for level 2 relationship. Default: <kbd class="ph userinput">2</kbd> |
| evt_mgmt.alert_insight_level_3_mapping | This property sets the score for level 3 relationship. Default: <kbd class="ph userinput">1</kbd> |
| Maximum related tasks ||
| evt_mgmt.alert_insight_max_tasks | Maximum related tasks to retrieve for alert insight. Default: <kbd class="ph userinput">10</kbd> |
[ ]

{#configure-alert-insight-properties__table_zm2_n3c_y2b}

## Metadata rules consideration {#configure-alert-insight-properties__section_htp_nkc_y2b}

The parent-child
relationship of CIs is considered. Dependent relationship rules consist of hosting and
containment rules, each type modeling the data from a different perspective of the CI.
To manage dependent relationship rules:

* To access rules at the class level, use the CI Class Manager. Navigate to AllConfigurationCI Class Manager.
* To access grouped rules, use the Metadata Editor. Navigate to AllConfigurationIdentification/ReconciliationMetadata Editor.

{#configure-alert-insight-properties__ul_itp_nkc_y2b}

Containment rules represent configuration hierarchy of CIs, describing which CI
contains which other CIs.

Hosting rules represent placement of CIs in a business
definition, describing what CIs run on.

Modify the alert insight properties to
configure the way alert information and analysis appears in the Alert Insight
pane.

## Related CIs configuration {#configure-alert-insight-properties__section_mpq_qkc_y2b}

The following properties control which CMDB relationships to consider for related CIs. The
CMDB relationships include regular CMDB relation rules, metadata rules (containment rules
and hosting rules), and suggested relations.
{#configure-alert-insight-properties__table_npq_qkc_y2b__entry__2}

| Property | Usage |
|-|-|
| evt_mgmt.related_cis_get_all_relation_types | Get all relation types, not including metadata rules. Default: <kbd class="ph userinput">false</kbd> |
| evt_mgmt.related_cis_use_containment_rules | Use metadata containment rules. Default: <kbd class="ph userinput">true</kbd> |
| evt_mgmt.related_cis_use_hosting_rules | Use metadata hosting rules. Default: <kbd class="ph userinput">true</kbd> |
| evt_mgmt.related_cis_use_suggested_relations_rules | Use suggested relations rules. Default: <kbd class="ph userinput">false</kbd> |
| evt_mgmt.related_cis_validate_relation_rules | This property controls whether to validate relation of CI according to metadata rules. Default: <kbd class="ph userinput">true</kbd> |
[ ]

{#configure-alert-insight-properties__table_npq_qkc_y2b}

## Score {#configure-alert-insight-properties__section_vlk_llc_y2b}

Scores are configured per relation type or depth. Scores are accumulated. The higher the
score, the more relevant is the related CI to the current CI.

Example:For a CI that was found at level <kbd class="ph userinput">2</kbd> in
the same application service of the current CI, the score is <kbd class="ph userinput">2</kbd>. The
same CI is in the same alert group, so there is an extra score of <kbd class="ph userinput">3</kbd>.
The accumulated score is therefore <kbd class="ph userinput">2+3 = 5</kbd>.

## Affiliation type {#configure-alert-insight-properties__section_tfg_plc_y2b}

The Affiliation Type column in the Related Incidents,
Related Change Requests, and Related Problems tabs shows the type of relationship that the CI of the selected alert
and the related CI have.

To see affiliation type relationships, navigate to AllConfigurationIdentification/ReconciliationMetadata Editor.

The parent-child relationship between configuration items is considered.

*[\>]: and then


