Docs » Introduction to alerts and detectors in Splunk Observability Cloud » Scenarios for finding and resolving infrastructure problems using alerts and detectors » Scenario: Kai monitors system limits with AutoDetect

Scenario: Kai monitors system limits with AutoDetect 🔗

Kai, a site reliability engineer at Buttercup Games, wants to know when they are reaching their limit for the number of detectors they can create for Buttercup Games. This limit is automatically monitored through an AutoDetect detector, which Kai can view from the Alerts and Detectors page.

View AutoDetect alerts and detectors 🔗

To use their AutoDetect detector, Kai must first find and view the details of the detector. The name of the detector is Splunk Operational – Number of detectors is expected to reach the maximum.

Kai finds the detector by following these steps:

  1. Kai opens the All alerts menu and unchecks Standard and Customized AutoDetect to filter for only AutoDetect detectors.

  2. Kai enters the name of the detector in the search bar.

  3. Kai selects the detector from the result list.

This screenshot shows the detectors search list with Kai's detector appearing as the first search result.

After Kai finds the AutoDetect detector that monitors the maximum number of detectors for Buttercup Games, they can set up alerts and add a preferred notification channel.

Subscribe to AutoDetect detectors 🔗

Kai wants to be alerted whenever their AutoDetect detector triggers an alert indicating that Buttercup Games has almost reached their maximum number of detectors. Kai can receive an alert from the system limits detector by subscribing to the detector.

To subscribe to an AutoDetect detector, Kai follows these steps:

  1. Kai finds their AutoDetect detector from the search list or their integration.

  2. Kai selects Add Recipients.

  3. Kai sets up the notification channel of their choice.

Kai will receive a notification whenever their AutoDetect detector triggers an alert for maximum number of detectors created.

Disable AutoDetect detectors 🔗

Kai decides that they no longer want to use their AutoDetect detector, as Buttercup Games has not come close to reaching their system limit. In this case, Kai can disable the detector by following these steps:

  1. Kai finds their detector from the search list.

  2. Kai selects Disable Detector. This stops the detector from reporting on data and Kai no longer receives notifications from the detector.

Customize AutoDetect detectors 🔗

Kai’s AutoDetect detector will trigger an alert when the number of detectors used is 90%, but Kai would like to be alerted when they are reaching 75% of the detectors used instead. To receive these alerts, Kai can customize the system limits AutoDetect detector.

To customize this detector, Kai follows these steps:

  1. Kai selects the Splunk Operational – Number of detectors is expected to reach the maximum detector.

  2. In the detector menu, Kai selects Create a Customized Version.

  3. Kai changes the Trigger threshold to 75%.

  4. Kai selects Activate.

Kai has created a new AutoDetect detector that will alert them whenever the number of detectors used reaches 75%.

Summary 🔗

In this scenario, Kai set up and subscribed to an AutoDetect detector that reported on system limits for Buttercup Games. Kai also learned how to find, disable, and customize the AutoDetect detector.

Learn more 🔗

For more information about AutoDetect detectors, see Use and customize AutoDetect alerts and detectors.

For information about AutoDetect integrations and types of AutoDetect detectors, see List of available AutoDetect detectors

This page was last updated on Oct 17, 2024.