How to Create an Alert Rule and Use Alerts in VectraOps How-To

VectraOps documentation

How to Create an Alert Rule and Use Alerts in VectraOps

This tutorial explains how to create a new Alert Rule in VectraOps, configure thresholds and time windows, enable or disable the rule, and how to view generated alerts right after saving.

Last updated January 16, 2026 vectraops alerts alert rules monitoring thresholds notifications operations

Tutorial: Creating Alert Rules and Using Alerts in VectraOps

VectraOps Alerts help you detect issues based on rule conditions (for example: availability, performance, or other monitored signals). Follow the steps below to create an Alert Rule and review alerts generated by the rule.

Before you start

  • You have access to the customer tenant.
  • The target systems have an active VectraOps agent installed and are reporting in.

Step-by-step: Create a new Alert Rule

  1. Log in to the customer tenant.
  2. In the left sidebar, open Alerts.
  3. Click Manage Alert Rules.
  4. Click Create new alert rule (+).
  5. Configure the rule:
    • Name — enter a clear, recognizable name for the rule.
    • Rule type — choose the rule type you want to create.
    • Window (minutes) — keep the default value unless your agent connects less frequently (for example, only once per hour). In that case, increase the window to match the agent reporting interval.
    • Thresholds — enter threshold values for alert types where applicable.
    • Description — add a short description explaining what the rule monitors and when it should trigger.
    • Status — enable or disable the rule.
  6. Click Save Rule.

After saving: what happens next?

NOTE: After the rule is created, it will immediately evaluate whether any alerts should be generated based on current system data.


View and use Alerts

  • Go back to Alerts in the sidebar.
  • Review the generated alerts list.
  • Open an alert to see details such as the affected system, the rule that triggered it, and any relevant values (for example, threshold vs. current value).

Recommended best practices

  • Use descriptive rule names (example: “High CPU > 90% (10 min)”).
  • Set the Window (minutes) to match how often systems report data.
  • Start with conservative thresholds, then tune them to reduce false positives.
  • Disable rules temporarily during maintenance windows if needed.