Alert System (Overview)

Alert Components

Each alert configuration consists of the following components:

• Alert Name: A clear and unique identifier for the alert.
• Text Description: A detailed explanation of the alert’s purpose.
• Exclusion Expression (MetricsQL): Defines conditions under which the threshold expression should be ignored.
• Suppression (Dropdown Menu): List of other alerts that, when active in any parent device, suppress this alert.
• Threshold Expression (MetricsQL): The core condition being evaluated.
• Severity Selection: Indicates the importance (e.g., Warning, Critical).
• Firing Delay: Numeric value specifying how long the condition must persist before the alert is triggered.
• Delay Time Unit: Time unit for the firing delay (seconds, minutes, hours, days).

Evaluation Logic

• Parallel Evaluation: Exclusion expressions are evaluated alongside the threshold expression.
• Exclusion Priority: If an exclusion expression returns a non-empty time series, the threshold expression is skipped.
• Suppression Logic: If any selected suppression alerts are active on any parent device, the current alert will not fire.

Alert Placement Guidelines

• Scope: Alerts should only be added to the Facility device. This is the top-level hierarchical element in the facility structure.

Activating Alerts for a Facility

Once alert configurations are created, they must be activated for specific facilities:

1. Open the Facility Digital Twin: Navigate to the facility where you want to activate alerts.
2. Go to the "Alerts" Section: In the Digital Twin interface, locate and open the "Alerts" section.
3. Add from Config List: Choose alerts from the list of available alert configurations to add them.
4. Activation: Any alert shown in the Alerts section is considered active and is evaluated automatically whenever new alert-relevant data arrives on the Platform.

Query Syntax

Reading Type Queries:

amp_readings_<readingType>{...}

Static Type Queries:

amp_statics_nominalPower{...}

Returns nominal power for a device or group.

Scope Definitions:

• {deviceId="{{DEVICE_ID}}"} → single device
• {facilityId="{{DEVICE_ID}}", deviceType="<type>"} → all children of a specific deviceType in a facility

Example Queries:

• Inverter Pac (facility scope):

amp_readings_Pac{facilityId="{{DEVICE_ID}}", deviceType="Inverter"}

• Irradiation (single device):

amp_readings_irradiation{deviceId="{{DEVICE_ID}}"}

MetricsQL Functions

You can use MetricsQL functions to extend expressions:

• avg_over_time(...)
• sum(...)
• median(...)
• etc.

Example Using WITH Block:

WITH(
  a = avg_over_time(amp_readings_Pac{facilityId="{{DEVICE_ID}} ", deviceType="Inverter"}[5m]),
  b = amp_statics_nominalPower{facilityId="{{DEVICE_ID}} ", deviceType="Inverter"}
)
a / b

Device Types

Alerts can be scoped to any of the following child deviceTypes using the scope expression. Common examples:

• Inverter
• Meter
• IrradiationSensor
• TransformerStation
• PanelString
• GridConnectionPoint

See full list: Device types

Reading Types

Threshold and exclusion queries are based on reading types. You may use any of the platform's supported readingTypes, such as:

• Pac, Qac, Uac, Iac
• irradiation, Temp, windSpeed
• energy, consumptionEnergy, importedEnergy
• PerformanceRatio, DeviationDaily, YieldLossTechnical

See complete list: Measured value types in formulas and alerts

Best Practices

• Name Clarity: Use descriptive names, e.g., Low Production PR < 0.85.
• Unit Awareness: Match delay timers with appropriate units (e.g., use minutes for short delays). Note that the minimum firing delay time is 10 minutes.
• Use WITH Blocks: Simplify complex queries for reusability.
• Suppress Wisely: Only use suppressions where alerts are redundant or hierarchically dependent.
• Exclude Wisely: typical suppression events are:
  • NB/DVM/unknown steering signals
  • Irradiation
  • Solar altitude angle
• Test Queries: Validate each MetricsQL expression in the Analysis Tool before saving.

Example Alert Configuration

Additional Resources

• For help writing expressions: MetricsQL Docs

Need More Help?

If you encountered any difficulties or need further assistance, here are some steps you can take:

Contact Support:

• Email: Reach out to our support team by emailing us at support@amperecloud.com. Provide as much detail as possible about the issue you're facing.

• Fill out a form: Complete our online support form. Please include all relevant information about your request, and our team will get back to you as soon as possible.

Share Your Feedback

If this article didn’t meet your needs or if you have suggestions on how we can improve, please let us know by submitting feedback. Your input helps us enhance our resources and support.