SN System Properties Reference
Property reference

evt_mgmt.self_health_use_glide_agg_for_duplicate_hashes

Selects how the duplicate-impact-hash health monitor checks for duplicates. By default, it uses predefined hash-name queries that exclude per-service hashes; enabling it includes those hashes but can slow checks on very large tables.

Default
false
Type
boolean
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? When enabled, the Duplicate Impact Hashes health monitor includes per-service hashes in its duplicate checks instead of using predefined hash-name queries.
What area does it affect? Event Management health monitoring
What does the default mean? The default value is "false", which means this behavior is disabled by default.
When should you review it? Review when duplicate checks need to include per-service hashes or when performance on very large tables is a concern.

Property record

No out of the box record exists. ServiceNow scripts read this property and use the default value shown until you create it.

Property name evt_mgmt.self_health_use_glide_agg_for_duplicate_hashes
Type boolean
Application Not stated
Default value false
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Used in

Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.

Health Monitor Script: Duplicate Impact Hashes The health monitor reads this setting to choose how it checks duplicate impact hashes. By default, it uses predefined hash-name queries, which do not cover hashes written per service; setting it to any value other than “false” includes those hashes but may be slower on very large tables. /em_monitor_scripts.do?sys_id=d3d666b807201110b34ce06b0fd3005b

More in evt_mgmt

Other properties in the same namespace.

evt_mgmt.self_health_duplicate_hashes_only_impact Restricts the Duplicate Impact Hashes health monitor to checking duplicate hashes whose names contain… evt_mgmt.self_health_monitoring.arm_execution_limit Sets the maximum number of alert executions the health monitor checks when assessing delays in incident… evt_mgmt.self_health_monitoring.ignore_frequently_updated_alerts When an alert meets the incident-creation delay threshold, enabling this setting skips frequently updated… evt_mgmt.self_health_monitoring.skip_event_diff Provides a numeric event-difference skip setting read by the self-health monitor, with a default value of 10. evt_mgmt.send_single_alert_to_subflow Chooses whether a running subflow receives a freshly retrieved alert record or the alert record already in… evt_mgmt.set_default_priority_group_for_alert_enabled When enabled, the alert-management fix script applies a default priority group to alerts. evt_mgmt.similarity_max_similar_alerts_shown This property sets the maximum number of similar alerts that can be shown in the alert details, enhancing… evt_mgmt.similarity_use_ml This property determines whether the Machine Learning model is utilized to find similar alerts, potentially…

All 217 properties in evt_mgmt →