{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30308,"path":"it-operations-management/event-management/configure-alert-insight-properties.md","title":"Alert insight properties","bundle":null,"doc_type":null,"release":"australia","body":"\n# Alert insight properties\n\nUse these properties to configure alert insight.\n\nThe role required: evt\\_mgmt\\_admin\n\nThe following alert\\_insight properties are under sys\\_properties.\n\n\n
\n\nProperty\n\n\n\nUsage\n\n
\n\nTime Frame\n\n
\n\nevt\\_mgmt.alert\\_insight\\_alert\\_history\\_min\n\n\n\nSet the time frame \\(in minutes\\) to retrieve repeated and similar alert data. Default `43200` \\(30 days\\)**Note:** Alerts are retrieved regardless of their state \\(open / reopen / flapping / closed\\).\n\n
\n\nevt\\_mgmt.alert\\_insight\\_closed\\_alert\\_window\n\n\n\nSet the time frame \\(in minutes\\) to retrieve alerts that were already closed. It is the time after the alert last updated date. Default: `4320` \\(3 days\\)\n\n
\n\nSimilarity\n\n
\n\nevt\\_mgmt.alert\\_insight\\_alert\\_same\\_as\\_filter\n\n\n\nThis property is a comma-separated string that defines which of the alert fields is used to consider alerts to be similar. Default: `source,type,resource,metric_name`\n\n
\n\nRelated CIs\n\n
\n\nevt\\_mgmt.alert\\_insight\\_related\\_cis\\_topology\\_levelsThe relationship types are:\n\n- CMDB based \\(metadata rules and suggested relations\\)\n- Within application services\n- Within Alert groups\n\n\n\nFor ‘Within application service’ relationship type, this property sets the depth or the maximum level of relationship of retrieved CIs. Default: `3`\n\n
\n\nScore\n\n
\n\nevt\\_mgmt.alert\\_insight\\_group\\_mapping\n\n\n\nThis property sets the score for within alert group relations. Default: `2`\n\n
\n\nevt\\_mgmt.alert\\_insight\\_level\\_1\\_mapping\n\n\n\nThis property sets the score for level 1 relationship. Default: `3`\n\n
\n\nevt\\_mgmt.alert\\_insight\\_level\\_2\\_mapping\n\n\n\nThis property sets the score for level 2 relationship. Default: `2`\n\n
\n\nevt\\_mgmt.alert\\_insight\\_level\\_3\\_mapping\n\n\n\nThis property sets the score for level 3 relationship. Default: `1`\n\n
\n\nMaximum related tasks\n\n
\n\nevt\\_mgmt.alert\\_insight\\_max\\_tasks\n\n\n\nMaximum related tasks to retrieve for alert insight. Default: `10`\n\n
## Metadata rules consideration\n\nThe 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.\n\nTo manage dependent relationship rules:\n\n- To access rules at the class level, use the CI Class Manager. Navigate to **All** > **Configuration** > **CI Class Manager**.\n- To access grouped rules, use the Metadata Editor. Navigate to **All** > **Configuration** > **Identification/Reconciliation** > **Metadata Editor**.\n\nContainment rules represent configuration hierarchy of CIs, describing which CI contains which other CIs.\n\nHosting rules represent placement of CIs in a business definition, describing what CIs run on.\n\nModify the alert insight properties to configure the way alert information and analysis appears in the Alert Insight pane.\n\n## Related CIs configuration\n\nThe 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.\n\n|Property|Usage|\n|--------|-----|\n|evt\\_mgmt.related\\_cis\\_get\\_all\\_relation\\_types|Get all relation types, not including metadata rules. Default: `false`|\n|evt\\_mgmt.related\\_cis\\_use\\_containment\\_rules|Use metadata containment rules. Default: `true`|\n|evt\\_mgmt.related\\_cis\\_use\\_hosting\\_rules|Use metadata hosting rules. Default: `true`|\n|evt\\_mgmt.related\\_cis\\_use\\_suggested\\_relations\\_rules|Use suggested relations rules. Default: `false`|\n|evt\\_mgmt.related\\_cis\\_validate\\_relation\\_rules|This property controls whether to validate relation of CI according to metadata rules. Default: `true`|\n\n## Score\n\nScores 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.\n\n**Example:**For a CI that was found at level `2` in the same application service of the current CI, the score is `2`. The same CI is in the same alert group, so there is an extra score of `3`. The accumulated score is therefore `2+3 = 5`.\n\n## Affiliation type\n\nThe 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.\n\nTo see affiliation type relationships, navigate to **All** > **Configuration** > **Identification/Reconciliation** > **Metadata Editor**.\n\nThe parent-child relationship between configuration items is considered.\n\n**Parent Topic:**[Manage and monitor alerts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/c_EMAlert.md)\n\n"}}