Tickets en aanvragen

Pieksignalen beoordelen

Review spike trigger · Define spike repeat action

Choose the task you want to carry out. Each procedure includes its prerequisites, steps and safeguards.

Voor wie

Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.

Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.

Review spike trigger

Review spike trigger.

Who can do this: Tenant administrator, Operator

Use an account with access to the stated page and permission for the chosen action.

The Trigger Store defaults to the Needs Review filter, which includes unreviewed and acknowledged triggers.
Stats refresh every 60 seconds, but trigger list data refreshes when filters change or after detail-panel actions.
Only unreviewed triggers can be acknowledged.
Only unreviewed or acknowledged triggers can be dismissed or assigned a new action.
A 409 response means another user or process already changed the trigger; the UI refreshes after showing the conflict warning.

Go to Configuration → Agent Settings → Spike detection.
Review the stats cards for Needs Review, Last 24 Hours, and Patterns Learned.
Use the status, affected service, and date filters to narrow the trigger list.
Open a trigger row to inspect the summary, cluster size, similarity score, affected service, sample reports, matched conversation count, and existing action.
If the trigger is real but still being assessed, acknowledge it.
If the trigger is noise or an acceptable duplicate pattern, dismiss it.
For an automatically created incident, use the available View Incident link.

Expected outcome: The user has reviewed the result of review spike trigger in the application.

Define spike repeat action

Define spike repeat action.

Who can do this: Tenant administrator, Operator

Use an account with access to the stated page and permission for the chosen action.

Only unreviewed or acknowledged triggers can be dismissed or assigned a new action.
The current form supports creating an incident or ignoring future repeats; do not assume additional action types are available.
A 409 response means another user or process already changed the trigger; the UI refreshes after showing the conflict warning.
Assignment group choices come from ITSM teams and can be left empty when creating an incident action.

Go to Configuration → Agent Settings → Spike detection.
Use the status, affected service, and date filters to narrow the trigger list.
Open a trigger row to inspect the summary, cluster size, similarity score, affected service, sample reports, matched conversation count, and existing action.
If the pattern should be learned, define an action: create an incident with priority and optional assignment group, or ignore future repeats.

Expected outcome: The user has reviewed the result of define spike repeat action in the application.

Dagelijkse support: tickets, e-mailbeoordeling, taken, uren en goedkeuringen.