Skip to content
Alle documentatie
Tickets en aanvragen

Piekdetectie instellen

Configure spike thresholds · Review spike detection status

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.

Taken

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

Configure spike thresholds

Configure spike thresholds.

Who can do this: Tenant administrator

Before you start

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

Safeguards

  • Spike detection is described in the UI as applying to conversations categorized as service disruptions.
  • Review similarity as the percentage shown in the interface.
  • Lower similarity thresholds catch looser matches but increase false positives.
  • Lower count thresholds create triggers more quickly but can turn small coincidences into review work.
  • Shorter time windows react faster; longer windows are better when reports arrive slowly.
  • Saving thresholds with detection disabled does not start detection.
  1. Go to Configuration → Agent Settings.
  2. Open the Spike Detection tab.
  3. Open the Spike Detection configuration wizard.
  4. On Enable, decide whether spike detection should be active.
  5. On Sensitivity, set similarity threshold, report count threshold, and time window.
  6. On Review, compare the selected settings with the server-provided defaults.
  7. Save the configuration.

Expected outcome: The user has reviewed the result of configure spike thresholds in the application.

Review spike detection status

Review spike detection status.

Who can do this: Tenant administrator

Before you start

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

Safeguards

  • Spike detection is described in the UI as applying to conversations categorized as service disruptions.
  • Lower similarity thresholds catch looser matches but increase false positives.
  • Lower count thresholds create triggers more quickly but can turn small coincidences into review work.
  • Shorter time windows react faster; longer windows are better when reports arrive slowly.
  • Saved settings alone do not mean detection is running.
  1. Go to Configuration → Agent Settings.
  2. Open the Spike Detection tab.
  3. Open the Spike Detection configuration wizard.
  4. Review whether detection is enabled and compare the saved thresholds and time window.
  5. Use the Trigger Store to monitor resulting triggers and tune settings after observing real trigger volume.

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

Aanbevolen werkwijze

  • Maak eigenaarschap duidelijk.
  • Gebruik statussen en prioriteiten consequent.

Gerelateerde handleidingen

Lees verder in Tickets en aanvragen

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