Duplicate / Delayed impact hashes

[Benjamin Jones]

Hi I was after some guidance I've seen the following Alerts come from EMSelfMonitoring

Duplicate impact hashes were found in sa_hash table

Delayed impact hashes where found in sa_hash table

and I've read through the KB about Impact Calculations and how to remedy what I've been seeing. What I'd like to know is what happens if these are not remedied and just left to continue producing events/alerts and what effects it will have.

Thanks in advance and apologies if this has been answered in a previous post.

[Vishal Savajia1]

A) Check with ServiceNow team, is there any backend process they have initiated. (Patch Upgrade or similar activity). Such activities may delayed JOB Execution. 

B) Kindly check too Event maintenance Record created on EVM for snoozing alerts. (Dynamic CI Group)

[Benjamin Jones]

Thank you greatly for replying. I shall speak with them to see if they have made any changes.

Is there any danger / what will happen if these are left unchecked and continue to produce Events

[Vishal Savajia1]

I believe we need to keep eye on it. It may not harm, but prevention is better than cure. it is good we can remediate it as early as possible.