Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Get started with the Collector for Kubernetes » Tutorial: Monitor your Kubernetes environment in Splunk Observability Cloud » Part 3: Activate a built-in detector to issue alerts

Part 3: Activate a built-in detector to issue alerts 🔗

Now that you have data flowing into Splunk Observability Cloud and you can explore that data using navigators and dashboards, you can set up an alert to help keep you informed about certain conditions in your data.

Create a detector 🔗

To create an alert, first create a detector that monitors your data for the conditions that you want to be alerted about. When these conditions met, the detector issues an alert.

  1. Access the chart you want to create a detector from. This example creates a detector based on the Memory Used % chart.

  2. Select the Get Alerts icon in the upper right of a chart. Some chart data have built-in templates that make it easy for you to create detectors for useful alert conditions. For example, in the Memory Used % chart, there is a detector template called Memory utilization % greater than historical norm.

    A user creates a new detector from a chart.

    This detector sends an alert when memory usage for the last 10 minutes was significantly higher than normal, as compared to the last 24 hours.

  3. The New Detector panel displays. Select Add Recipients to add an email, Splunk Observability Cloud team, or webhook that you want to receive the alert. See Create and manage teams in Splunk Observability Cloud and Send alert notifications to a webhook using Splunk Observability Cloud to learn more.

    A screen shows a summary of the new detector and alert condition.
  4. Select Activate. When the data condition is met, Splunk Observability Cloud sends a notification to designated recipients and displays alerts on the Alerts page.

    An alert that the new detector triggered.

This completes the tutorial. You deployed the Splunk Distribution of the OpenTelemetry Collector on a Kubernetes cluster, viewed your cluster data, and created a detector to issue alerts.

Learn more 🔗

This page was last updated on May 28, 2024.