Skip to main content

How to Create an Alert (Advanced)

Discover how to create more advanced Alerts in Guidewheel

M
Written by Mitchell Grathwohl
Updated this week

Overview

Advanced alerts in the Issues module allow teams to monitor more specific conditions beyond basic downtime, idle, or offline states. Using Overloaded and Custom conditions, you can track machine thresholds, power metrics, or production rates. This article explains how to configure these advanced alert types and best practices for using them.

Prerequisites

  • Admin permissions (only admins can create alerts)

  • Access to the Issues module

  • Rated thresholds or performance metrics set up for your devices

  • (Optional) Work with your Technical Account Manager or Customer Success Manager to enable custom metrics

Step-by-Step Instructions

1. Access Advanced Alert Options

  1. Go to Issues > Alert Settings.

  2. Click New Alert.

  3. Choose either Overloaded or Custom under condition types.

2. Configure Overloaded Alerts

  1. In the Overloaded condition, set an upper limit threshold for a device.

    • Example: If a motor runs above its rated load, trigger an alert.

  2. To set thresholds:

    • Go to Device > Edit > Threshold.

    • Enter the rated upper limit for runtime or performance.

    • Save changes.

  3. The threshold will also display on the Uptime page once saved.

  4. Return to Alert Settings to finish creating the alert.

3. Configure Custom Alerts

  1. Select Custom from the alert conditions.

  2. Choose from available metrics (varies by installation):

    • Electrical: active power, current, frequency, voltage (line-to-neutral)

    • Performance: feet per minute, units per second, bags, bottles, etc.

  3. Define the condition:

    • Select average, max, or min.

    • Choose greater than or less than.

    • Enter the threshold value.

  4. (Optional) Use AND/OR logic to combine multiple conditions.

  5. Assign a tag (e.g., “Overloaded” or “High Power Usage”) for easier tracking in reports.

4. Save and Review

  1. Review the alert details to ensure they don’t conflict with existing alerts.

  2. Save the alert.

  3. Test by reviewing generated issues in the Issues tab and confirming correct tagging.

Tips & Best Practices

  • Always assign a unique tag to advanced alerts so they can be easily filtered in Analysis.

  • Avoid overlapping conditions with basic Down alerts to reduce duplicate issues.

  • Use Overloaded alerts to protect auxiliary equipment from running above rated capacity.

  • Use Custom alerts to track production-specific metrics (e.g., line speed or output).

  • Collaborate with your Guidewheel support team to ensure proper setup of thresholds and metrics.

Troubleshooting

  • No advanced options available → Contact your Customer Success Manager to confirm custom metrics are enabled.

  • Overloaded alert not triggering → Check that device thresholds are set correctly under Device > Threshold.

  • Duplicate alerts created → Review existing alerts and refine conditions to avoid overlap.

  • Incorrect tags on issues → Confirm that the alert is set to auto-tag issues properly

Did this answer your question?