Alert Rules
A rule answers three questions: what it watches, when it fires, and where — on which plants. Open Alert Manager ▸ Rules and click New rule, or click a rule to change it. Open in Mirox
Changes take effect on the plants at once. A rule can be switched off with its toggle in the list — it then stops being checked and its open alerts resolve.
The Metric
Under What it watches you choose the value the rule observes:
- Platform series — the values Mirox records for every plant, such as the AC power of the inverters, the grid feed-in or the irradiance. Each is offered with its unit.
- Your metrics — the metrics your organization defined. A rule uses a metric exactly as a report would; if the metric is changed, the rule follows.
The field opens the same metric list as Data Export: search by name, description or id, grouped like there, and every row shows its unit, the steps it is recorded at, the plant types it exists on and — behind ⓘ — what it measures. The metric you chose is explained right under the field.
Then choose how the metric is judged:
- Plant total — one value for the whole plant, so one alert per plant.
- Each component — one value per inverter, combiner box, string or other component the metric reports on, so one alert per component that meets the condition. This is only offered for metrics that report per component.
Components you have hidden on the plant are left out: no alert opens for them, and an open alert closes when its component is hidden.
When It Fires
- Value — Latest value compares the most recent value. Over the last … min first folds the metric over that window — in the same way the metric folds in a report (average, sum, share, …) — and compares the result. The window is whole quarters of an hour.
- is — above, at or above, below, at or below, equal to, not equal to.
- Threshold — the number to compare with, in the unit shown.
- For at least (min) — the condition must hold without interruption for this long before the alert opens. Until then the alert is pending. Durations are multiples of 5 minutes.
- Clears only at (optional) — a second threshold for resolving. Without it the alert resolves as soon as the condition no longer holds. With it — for example fires below 10, clears only above 50 — a value hovering around the threshold does not open and close the alert again and again.
- Keep firing for (min) — keeps the alert open for this long after the condition cleared; a short dip back to normal does not resolve it.
Several times within a window
Switch on Fire when it happens several times to alert on something that keeps coming back rather than something that lasts. The rule then counts how often the condition started within the window — for example 3 times within 60 minutes — and fires when that number is reached. It resolves once the count in the window falls below it again.
When There Is No Value
If the metric has no value, the rule does what you choose — whether the plant sends no data or the value does not exist for this plant (for example the compensation of a plant without an agreed compensation):
- No alert — no value is never an alert; an open alert resolves.
- Alert — missing data is itself the alert, for example to notice a meter that stopped reporting. Like a condition, it opens only once the data has been missing for the rule's For at least duration, so one late value does not alert.
- Keep last state — an open alert stays open, a quiet rule stays quiet, until values arrive again.
A plant whose whole agent stops reporting is covered separately: it raises Alert rules not checked — see Engine status.
Only at Certain Times
Under Only during (plant time) you limit the rule to weekdays and to a time of day, in the plant's local time. No days and no hours mean always. A range such as 22:00 – 06:00 spans midnight. Outside the schedule the rule is not judged and an open alert resolves.
Choose Sunrise / sunset instead of a clock time for anything that depends on daylight. The rule is then active from sunrise plus the first offset to sunset plus the second, computed every day at the plant's location; positive minutes mean after, negative minutes before. +60 / −60 runs from one hour after sunrise to one hour before sunset, so the window follows the seasons without being adjusted. The weekdays still apply. On a day the sun does not rise at the plant the rule is not judged.
Level
Every rule sets the level of its alerts, from Very low to Critical — the same six levels the platform uses, described in Alarm Levels. The level decides who is notified, because everyone chooses in their own settings from which level on they want to hear about Alert Manager alerts.
Which Plants
All plants, the plants of chosen portfolios, or chosen plants. A plant can be targeted by at most 50 rules; an organization can have up to 500 rules.
If a rule cannot be checked on a plant — for example because the metric needs a series that plant does not record — the editor lists the plant under Not evaluated on some plants with the reason.
Except these plants leaves single plants out of all plants or of a portfolio — the rule never watches them, whatever else selects them.
Notification and Alert Text
Everyone in your organization who has access to the plant is notified according to their own notification settings (group Alert Manager). Under Receivers you add automated targets on top — see Receivers.
Switch off Notify users for an alert that is meant for systems only: the rule then sends to its receivers, and nobody in your organization is notified. The alerts still appear on the Alerts tab.
Alert text is the one line shown with every alert. Placeholders are filled in for each alert:
| Placeholder | Becomes |
|---|---|
{component} | the component, e.g. Inverter 3 (empty for a plant total) |
{value} | the value that was judged, with its unit |
{threshold} | the threshold, with its unit |
{park} | the plant name |
{rule} | the rule name |
Example: {component} delivers only {value} (limit {threshold}).
Replay on a Plant
At the bottom of the editor, Replay on a plant shows what the rule would have done over the last 1, 2, 3 or 7 days on a plant you pick: the watched values, the threshold, and every period in which an alert would have been open. It is decided by the same engine the plant runs, so what you see is what the plant will do. Use it before saving, to find a threshold that fires when it should and stays quiet otherwise.
If the plant delivered no values for the metric in that period, the replay says so — pick another plant or a longer period.
History on your plants goes further: it replays the rule on every plant it targets over the last day, 30 days or year — on the same 5-minute grid the plants evaluate, exact also for a whole year — and shows per plant how often it would have alerted, for how long in total, and every alert on a timeline; hover one for its start, end, duration and extreme value. Use it to find false alarms before you save.