Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

Monitor Flow on Helios with Alerts

On this page

Flow alerting in SingleStore Helios monitors the health and activity of Flow instances associated with a cluster. Flow-specific trigger conditions are configured on the Alerts page for a cluster, where severity levels, thresholds, and email subscribers for each alert can be set.

When Flow alerts are enabled for a cluster, the configured alert rules apply to all Flow instances mapped to that cluster. When a rule's threshold is met for any Flow instance, Helios sends email notifications to the cluster's alert subscribers.

The Flow-specific trigger conditions are:

  • Flow CPU Utilization: Triggers an alert when CPU usage for at least one instance is above a configured threshold for a specified duration.

  • Flow Memory Utilization: Triggers an alert when memory usage for a Flow instance is above a configured threshold for a specified duration.

  • Flow Inactivity: Triggers an alert when a Flow instance has not moved any records for a configured period of time.

  • Flow Scheduler Error: Triggers an alert when the scheduler for a Flow instance enters an error state.

For general alerting concepts (severity levels, thresholds, and subscribers), refer to Alerts.

Prerequisites

  • Flow on Helios version 4.3.6 or later.

Configure Flow Alerts

To configure Flow alert rules for a cluster:

  1. In the Cloud Portal, navigate to Monitoring > Alerts.

  2. At the top of the page, select the cluster group that contains your cluster.

  3. In the Alerts Configuration table, locate the row for your cluster.

  4. In the Actions column for that cluster, click the Edit icon. This opens the alert configuration, including Flow-related trigger conditions for that cluster.

  5. In the Edit Alert Rules dialog, scroll to the Flow alert types:

    • Flow CPU Utilization

    • Flow Memory Utilization

    • Flow Inactivity

    • Flow Scheduler Error

  6. For each Flow alert type that is required:

    1. Enable it

    2. Configure the severity levels (Critical, Warn, Info) with appropriate thresholds and durations

    3. For Flow Scheduler Error, toggle it on (it functions as an on/off rule)

  7. In the Subscribers section of the alerts configuration, add or update the list of email addresses that should receive alerts for this cluster. 

  8. Click Save to apply the alert configuration. 

Once saved, the Flow alert rules are enforced for every Flow instance mapped to the cluster. When a configured condition is met, Helios sends email notifications according to the severity and the existing alerting behavior documented for clusters.

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In