How are you segregating the high cpu usage??
is it by warning(80&-90%) and critical(>90%).
For creating a new ticket in SNOW,a parameter called sys_id is very important,If correlationid is unique,then sys_id will be unique,then it will create new ticket,else it should just update the existing one,without any notification.
Now assume you have an instance,for warning,when alert is raised and ticket is created in SNOW with sys_id.
Assume sys_id is "A" .
Once you resolve the ticket,then again an alert should be raised with warning state,but it will not raise a new ticket,it just updates the short_description.
So ideally for an instance only 2 ticket will logged for warning and critical state.
Aren't you facing this problem??this is what i'm facing...
... View more