Alerts & Notifications
Alerts
Alert Manager ▸ Alerts lists the alerts your rules raised. Open in Mirox By default you see what fires right now; two switches widen the list:
- Show resolved — adds the alerts that have ended, as history.
- Show silenced — adds the alerts a silence holds. Silenced alerts are hidden by default, firing or resolved, so the list shows what somebody still has to look at; the Overview counts them apart from the firing alerts as + N silenced.
Each alert shows its level, the rule, the plant, the component (for rules judged on each component), the value, and since when — or from when to when — it fired; dates and times follow the language and region settings of your browser. The plant and the component are links to their pages. An alert of a rule judged on the plant total offers Which components?: it replays the rule per component over the alert's window and lists which ones were behind it. An alert a silence holds is marked Silenced.
An alert resolves by itself when the condition no longer holds, when the rule is switched off, changed so that it no longer matches, or deleted. Resolved alerts stay in the list as history.
Who was notified, who has seen it
Notified and Seen by in the alert's details show who the platform notified of the alert and when, and who has opened it since — opening the details records you there. There is nothing to confirm: an alert ends by itself when the condition no longer holds.
Silence an alert from its details
Silence this alert in the alert's details keeps exactly this alert quiet without opening the Silences tab. Pick how long — 1 h, 4 h (the default), 8 h, 24 h, 3 d or 7 d — and a silence is created for this rule, this plant and this component (the plant total when the alert is plant-wide). The alert is marked Silenced at once and nobody is notified while the silence holds. If the alert still fires when the silence ends, it is notified then — the silence postpones, it does not swallow. An alert that was already notified before it was silenced still sends its resolution notice. The details link to the silence under Open the silences, where it can be extended, widened or removed.
Rule and silence changes also appear in your organization's activity.
Who Is Notified
When an alert opens, everyone in your organization who has access to the plant is notified — in the app, by push on the mobile app and by email, exactly as each person chose in their own notification settings under the group Alert Manager. There everyone picks the channels and the minimum level from which they want to hear about these alerts; by default it is Normal.
When the alert resolves, the people who were notified receive a resolution notice. The notification links straight to the alert.
Silences
A silence keeps notifications away for a while — for maintenance, a known problem or a planned shutdown. Matching alerts still open and close and are recorded, marked Silenced (and hidden from the Alerts tab until you Show silenced); only the notifications and receivers stay quiet.
Open Alert Manager ▸ Silences and click New silence. Open in Mirox Choose:
- Rule — one rule, or every rule.
- Plant — one plant, or every plant.
- Starts — now, or at a planned time.
- For — from 1 hour up to 1 year, or Until a date… for a free end date (at most one year after the start).
- Comment — why, so your colleagues know.
While you choose, the dialog counts live how many open alerts match — N open alerts would be silenced now — so you see what the silence will take hold of before you create it. A silence that starts now takes hold of the matching open alerts immediately.
The table shows for every silence its rule, plant, start and end, comment and state — Active, Planned or Ended — and Suppressing: the number of open alerts the silence holds right now.
A silence can be edited from its row (Edit): rule, plant, start, end and comment. The change takes hold at once — alerts the silence newly matches stop notifying, alerts it no longer matches notify again from the next evaluation. A silence that was created from a single alert covers only that alert's component (or the plant total); under Component it can be widened to Every lane of the rule and plant, but not narrowed to another component.
A silence ends by itself. Remove it earlier with Remove — matching alerts are notified again from the next evaluation on, including those firing right now. Silences are created, edited and removed by Admins, Moderators and the two Asset Manager roles.
Receivers
A receiver gets every alert of the rules it is attached to, automatically — a ticket system, a team channel or a shared mailbox. People do not need a receiver; they are notified through their own settings anyway. You create two kinds yourself, Webhook and Email; a direct marketer set up under Organization becomes a receiver on its own — see Direct marketer.
Open Alert Manager ▸ Receivers and click New receiver Open in Mirox, then attach it to rules under Receivers on the Notification tab of the rule editor. Send test delivers a sample alert — with a sample outage report in it — so you can check the connection and your template; a direct marketer offers Test sign-in instead, which signs in at the marketer's web service. A receiver can be edited afterwards from its row menu (Edit) — the name, the addresses or the webhook address and template, whether the resolution is sent too (Also send the resolution); only its type is fixed. Rotate signing secret issues a new webhook secret, shown once like on creation. A receiver that was disabled after repeated delivery failures (badge Disabled) is switched on again with Re-enable. A direct marketer's receiver is managed under Organization ▸ Direct marketers; in the Receivers tab it offers only Test sign-in and its active switch. In the rules table each receiver appears as a chip; hovering it names the receiver and the template it sends with (an email receiver without one: Built-in text).
A list of email addresses. Each alert and its resolution arrive as one email.
Webhook
An HTTPS address plus a template: the address receives a POST for each alert and its resolution, shaped by the receiver's template — the method, the headers and the body it sends. The receiver takes one of your organization's webhook templates — the dialog lists them, when you create the receiver and when you edit it; if there is none yet, create one first under Templates. The examples there cover Microsoft Teams, Slack and Discord as well as your own JSON, XML and CSV: the Generic JSON (signed envelope) example — the full alert as JSON, see below — is the base for ticket systems and your own automation; Microsoft Teams card, Slack message and Discord embed are ready-made messages for an incoming webhook of those services, whose address is then the receiver's address (Slack hooks.slack.com/services/…, Discord discord.com/api/webhooks/…, Teams Workflows *.environment.api.powerplatform.com or *.logic.azure.com — see Connect Microsoft Teams for how to create one). A Teams Workflows webhook rejects an Authorization header — do not add one to a template for Teams.
When you create a webhook receiver, its signing secret is shown once. Every request is signed: it carries the header X-Mirox-Signature: sha256=<hex> — the HMAC-SHA256 of the raw request body with that secret — plus X-Mirox-Timestamp and a unique X-Mirox-Delivery-Id, together with the template's own headers, whatever the address. Check the signature before you trust a request, and use the delivery id to ignore a repeated delivery. Chat services such as Teams, Slack and Discord simply ignore the X-Mirox-* headers.
The body of the ready-made Generic JSON (signed envelope) template:
{
"version": "1",
"status": "firing",
"event_id": "1216448682925686786",
"rule_uid": "A1B2C3D4E5F6",
"rule_name": "Inverter without power",
"rule_version": 3,
"priority": "high",
"park_uid": "0A1B2C3D4E5F",
"park_name": "Plant North",
"instance_key": "inverter_id=7",
"labels": { "inverter_id": "7" },
"component": "Inverter 7",
"metric": "AC power per inverter",
"value": 0.0,
"unit": "W",
"op": "lt",
"threshold": 10.0,
"condition_since": 1791200400,
"title": "[FIRING] Inverter without power — Plant North (Inverter 7)",
"body": "Inverter 7 delivers only 0 W (limit 10 W)",
"link": "https://service.mirox.io/#/alertmanager?tab=alerts&alert=1216448682925686786",
"sent_at": "2026-10-06T09:05:12+00:00"
}
status is firing or resolved; a resolution repeats the alert with the last value judged. condition_since is a Unix timestamp. Fields may be added in later versions — ignore what you do not know. event_id is a string — the id is longer than a JavaScript number can hold exactly.
After repeated failed deliveries a receiver is switched off and marked Disabled; check the address, then Re-enable it from its row menu.
Addresses Mirox calls
Mirox connects to a webhook address only over HTTPS on port 443, and only if the address resolves to a public IP address. Other ports (such as 8443), plain http:// and private or internal addresses (10.x, 172.16–31.x, 192.168.x, localhost and similar) are refused. If your endpoint listens on another port or can only be reached inside your network, put a reverse proxy in front of it that is publicly reachable on port 443 — or contact our support if that is not possible for you.
Direct marketer
A direct marketer is set up once under Organization ▸ Direct marketers Open in Mirox: a name, the protocol it speaks — today the BWE outage interface; Request another protocol sends us the name of the standard your marketer uses — the web service and sign-in addresses, the credentials the marketer issued and the hours ahead it wants an outage reported (2 by default, 1 to 48). Each row ends with a … menu: Edit, Test sign-in, Receiver in the Alert Manager and Delete. Test sign-in signs in at the marketer and shows how many plants it has assigned to your account; it never reports an outage. A wind plant picks the marketer it sells through on its Unavailability page — see Unavailability and the Direct Marketer.
Addresses Mirox calls
Mirox connects to the marketer's web service and sign-in addresses only over HTTPS on port 443, and only if they resolve to a public IP address. Other ports (such as 8443), plain http:// and private or internal addresses are refused. If your marketer's service is reachable only on another port, ask the marketer for an address on port 443 — or contact our support.
The marketer automatically becomes one receiver in the Alert Manager, with its name. It cannot be created from New receiver (that dialog offers webhook and email only) and never exists twice; renaming the marketer or switching it off is mirrored on the receiver, deleting the marketer removes it, and setting the marketer up again brings it back. In the Receivers tab the row is read-only — Managed under Organization ▸ Direct marketers — apart from Test sign-in and its active switch, both reserved to Admins and Moderators. It has no template: the protocol dictates what the marketer gets.
The rule reports the outage. On a rule that watches the turbines of a wind plant one by one (judged on each component of a turbine metric), the Notification tab offers the switch Report outages. With it on, every firing turbine alert of the rule is an outage of that turbine from the moment it opens: an outage start, reported the hours ahead; a renewal about every half of those hours while the alert keeps firing; and the end, cut back to the real end, when it resolves. Next to the switch you choose the outage reason — Maintenance, Administrative order, Grid operator or Direct marketer — and the remaining power: Full stop (0 kW) or the measured value, the alert's power value capped at the turbine's rated power, for a rule on a power metric. Use Grid operator and Direct marketer only when the source of the curtailment is certain — they count as compensated curtailments in the settlement, the other two lower the turbine's availability. The hours ahead are those of the plant's marketer when the rule reports to it, otherwise 2. The switch is forced on, and shown locked, while the marketer's receiver is attached; a rule judged on the plant total does not offer it and is never reported. A plant that another organization shares with you by a cooperation can be reported too: every organization reports with its own rules and its own direct marketer, independently of the plant's owner — the rule names the marketer through its receiver.
Every receiver of the rule gets the three moments — start, renewal and end — and nothing else: your own email or webhook receiver gets them rendered through its template with the outage.* variables (or as a built-in text without one), and the marketer's receiver gets them through its protocol, sent by the plant's agent. A rule that reports outages does not send its receivers the usual firing and resolution messages on top; the people of your organization are notified as always, and a test run never reports an outage.
That is how you test first and switch later: build the rule with your own email or webhook receiver and watch start, renewal and end arrive in your mailbox or at your endpoint — exactly what the marketer would get. When you are satisfied, open the rule's Notification tab, remove your receiver (or keep it) and add the marketer's receiver. Nothing else changes — the rule, the reason, the remaining power and the hours ahead all stay; from the next pass on, the plant reports every open outage to the marketer, from its original beginning.
Which plants reach the marketer follows from the plants: a plant reports through the marketer linked on its Unavailability page, so the marketer's receiver reports exactly those plants of the rule that are linked to it. For a plant linked to another marketer or to none, the outage is recorded in the plant's register and sent to your own receivers, but not to a marketer — the rule editor names those plants on the Notification tab. It also says when a plant's agent still needs an update for outage reports: until then the rule's receivers get the alert itself, as with an ordinary rule.
The system templates for turbines come with the switch on and attach your marketer's receiver when you adopt them — see Examples. On the plant, the outages appear in the Unavailability register as Reported by alarm, and the Reported live by alarm card on the plant's Direct marketer tab lists every rule that reports the plant — rule, reason, remaining power, hours ahead and whether it reaches the marketer — with the badge Inactive for a switched-off rule.
What was delivered
An alert's details list its Deliveries: one row per receiver and moment — firing or resolved for an ordinary rule, start, renewal or end for an outage report — with the time and whether it was sent, failed (with the error) or skipped, and why: a silence, the receiver switched off, resolutions not wanted, the outage report taking the place of the alert message, or — for a resolution — that the alert itself never reached the receiver. When one rule opens many alerts at once (a rule on each of hundreds of strings at dusk), its notifications and receiver messages pause after the first four within an hour, for 30 minutes, and the people are told in one summary instead; an alert that was never sent to a receiver sends it no resolution either. For the marketer's receiver the row shows what the plant reported and the window it covers. When a receiver fails, your organization gets the event Receiver failing, addressed to the Admins and Moderators and to the authors of the rules that use the receiver; after ten failed deliveries in a row the receiver is switched off (Receiver switched off), and the event closes by itself once a delivery succeeds again — fix the cause, then Re-enable the receiver from its row menu. The marketer's receiver reports the health of the marketer connection the same way.
Templates
A template designs exactly what a receiver sends, so any system gets the format it expects: for a webhook the method (POST, PUT or PATCH), your own headers and the body in JSON, XML, CSV, HTML, plain text or form data; for an email the subject and the text (plain text or your own HTML). A direct marketer's receiver has no template — its protocol dictates the report; what a rule that reports outages sends to your email and webhook receivers is shaped by their templates, with the outage.* variables. You write fixed text and insert variables of the alert, the rule, the plant and the component. A template is reusable: several receivers can use the same one, and a change applies to all of them at once.
Open Alert Manager ▸ Receivers Open in Mirox: below the receivers you find your Templates and the examples to start from. Use example copies one into your organization; New template starts empty. The ready-made webhook templates — the Generic JSON (signed envelope) and the chat messages for Microsoft Teams, Slack and Discord — are started from the examples like every other; the receiver dialog lists only your organization's own templates. The template opens in the builder: on the left the settings, the headers and the body, in the middle the list of variables — a click inserts the variable at the cursor — and on the right the live preview: the request or email exactly as it would be sent, with the sample alert or one of your recent alerts, and every error or warning. Then choose the template for a receiver — when creating it, or with the template button in its row. A webhook receiver always sends with a template; an email receiver without one sends the built-in text.
The Mirox email frame is your choice. A plain-text email template has the switch Send inside the Mirox email frame (on by default): on, your text is placed in the Mirox mail — heading, a button to the alert, footer and "mirox |" in front of the subject; off, subject and text go out exactly as rendered, nothing added. An HTML template is always sent as it is. The preview is always the mail as it arrives — with the frame on it shows the complete framed mail — and it offers three more sources next to the sample alert and your recent alerts: a sample outage report at its start, renewal and end, so a template for a rule that reports outages can be checked with every field filled. Under the preview a note says whether the rendered outage group was reported by the digital twin or derived from the alert, and which fields stay empty in that case.
Templates are created, duplicated, changed and deleted by Admins, Moderators and the two Asset Manager roles; every member can view them. A template marked Private is changed only by its creator, an Admin or a Moderator — see Private. A template that a receiver uses cannot be deleted — choose another one for that receiver first.
The template language
| Write | Meaning |
|---|---|
Variable: {{plant.name}} | the value, e.g. the plant name |
Filter: {{alert.since|date:"DD.MM.YYYY HH:mm"}} | the value, formatted |
Section: {{#alert.firing}}…{{/alert.firing}} | the part between only when the value is set — for a list once per item |
Inverted section: {{^component.name}}…{{/component.name}} | the part between only when the value is empty |
Comment: {{! … }} | nothing — a note for you |
Literal braces: \{{ | {{ as text |
Inside a list section, {{@index}} (from 0), {{@number}} (from 1), {{@first}} and {{@last}} are available — for example {{^@last}},{{/@last}} puts a comma between items. A variable that does not exist stays empty, and the preview lists it as a warning. Nothing in a template is executed; it only ever produces text.
Variables
| Variable | Meaning |
|---|---|
{{alert.id}} | Alert id (a string) |
{{alert.status}} | firing or resolved |
{{alert.firing}} | True while the alert fires (use as a section) |
{{alert.resolved}} | True for the resolution notice |
{{alert.level}} | Level: very_low, low, normal, high, very_high, critical |
{{alert.title}} | The ready one-line title |
{{alert.text}} | The ready one-line message |
{{alert.summary}} | The rule's own summary text, if it has one |
{{alert.value}} | The value judged (the last one on resolution) |
{{alert.value_label}} | The value with its unit, as shown in Mirox |
{{alert.value_kw}} | The value in kW — only for a power metric (W, kW, MW) |
{{alert.unit}} | The metric's unit |
{{alert.threshold}} | The rule's threshold |
{{alert.threshold_label}} | The threshold with its unit |
{{alert.threshold_kw}} | The threshold in kW — only for a power metric |
{{alert.op}} | Comparison: gt, ge, lt, le, eq, ne |
{{alert.op_symbol}} | The comparison as a symbol (>, ≥, <, ≤, =, ≠) |
{{alert.since}} | When the condition started |
{{alert.until}} | When the alert resolved (empty while it fires) |
{{alert.duration_s}} | Seconds from since to until (or to now) |
{{alert.close_reason}} | Why it resolved: condition, rule_disabled, rule_removed, … |
{{alert.silenced}} | True when a silence matched |
{{alert.link}} | Absolute link to the alert in Mirox |
{{alert.instance_key}} | The alert's instance (component labels) |
{{rule.uid}} | Rule id |
{{rule.name}} | Rule name |
{{rule.description}} | Rule description |
{{rule.version}} | Rule version that raised the alert |
{{rule.window_s}} | Rule window in seconds (0 = each value) |
{{rule.for_s}} | How long the condition must hold, in seconds |
{{rule.metric.name}} | Metric name |
{{rule.metric.unit}} | Metric unit |
{{plant.uid}} | Plant id |
{{plant.name}} | Plant name |
{{plant.type}} | Plant type: solar, wind, battery |
{{plant.timezone}} | Plant time zone (dates use it by default) |
{{plant.peak_power_kw}} | Installed peak power in kWp |
{{plant.grid_limit_kw}} | Grid connection limit in kW, if set |
{{plant.inverter_limit_kw}} | Inverter power limit in kW, if set |
{{plant.latitude}} | Latitude |
{{plant.longitude}} | Longitude |
{{plant.portfolio.uid}} | Portfolio id |
{{plant.portfolio.name}} | Portfolio name |
{{plant.address.street}} | Street (address line 1) |
{{plant.address.street2}} | Address line 2 |
{{plant.address.zip}} | Postal code |
{{plant.address.city}} | City |
{{plant.address.state}} | State / region |
{{plant.address.country}} | Country |
{{plant.grid_operator}} | Grid operator, if entered |
{{plant.project_company}} | Project company, if entered |
{{plant.market_zone}} | Market (bidding) zone, if entered |
{{plant.commissioning_date}} | Commissioning date, if entered |
{{component.name}} | Component name (empty for a plant-wide rule) |
{{component.id}} | Component id in Mirox, if known |
{{component.kind}} | Component kind (inverter, string, …) |
{{component.labels}} | The component labels as an object |
{{component.labels_list}} | The labels as a list of {name, value} for a section |
{{organization.uid}} | Organization id |
{{organization.name}} | Organization name |
{{delivery.id}} | Unique id of this delivery (also in X-Mirox-Delivery-Id) |
{{delivery.receiver}} | Name of the receiver |
{{delivery.test}} | True for a test send |
{{now}} | The moment of sending |
Every delivery carries the group outage, and it is never empty. On an ordinary alert it is derived from the alert itself: the unit is the alert's component (a turbine), begin is the first moment the condition held, end the resolve, reason and remaining power come from the rule's outage settings — and outage.reported is false. On a rule that reports outages the plant's digital twin takes over and reports the outage: a window ahead, renewed while the alert keeps firing, ended at the resolve — only then are reported, renewed, reported_until, horizon_hours, marketer.name and register_link filled; on a plain alert they stay empty or false. {{#outage.reported}}…{{/outage.reported}} tells the two apart in one template. The serial number, plant key and rated power are the plant's master data and stay empty where none are entered. The rule editor warns when a template of its receivers reads a reported-only field on a rule that does not report:
| Variable | Meaning |
|---|---|
{{outage.reported}} | True when the plant's digital twin reported this moment as an outage (rule with outage report); false when the group is derived from the alert alone |
{{outage.moment}} | What this delivery announces: start (the alert fired), renewal (reported window extended — reported outages only) or end (the alert resolved) |
{{outage.started}}, {{outage.renewed}}, {{outage.ended}} | True for that moment (use as sections) |
{{outage.begin}} | When the outage began |
{{outage.end}} | The real end once the alert resolved (empty before) |
{{outage.reported_until}} | End of the window reported so far — renewed before it runs out (reported outages only; empty on a plain alert) |
{{outage.horizon_hours}} | How many hours ahead the outage is reported (reported outages only; empty on a plain alert) |
{{outage.reason}} | Reason code: ADMINISTRATIVE, MAINTENANCE, GRID, MARKET |
{{outage.reason_label}} | The reason in words |
{{outage.available_power_kw}} | Remaining power of the turbine in kW (0 = full stop) |
{{outage.comment}} | The report's comment (the rule's name) |
{{outage.marketer.name}} | The direct marketer the rule reports to through its marketer receiver (empty on a plain alert or a rehearsal without one) |
{{outage.unit.name}}, {{outage.unit.id}} | Name and id of the turbine |
{{outage.unit.serialnumber}}, {{outage.unit.manufacturer_id}}, {{outage.unit.plant_key}} | Serial number, manufacturer id and plant key from the master data, if entered |
{{outage.unit.rated_kw}} | Rated power of the turbine in kW |
{{outage.register_link}} | Link to the plant's outage register in Mirox |
Dates are shown in the plant's time zone unless the date filter names another one. The plant has no field for a MaStR number or a market location — write such identifiers into the template as fixed text.
Filters follow the variable after | and can be chained, for example {{alert.value|kw|number:1:de}}:
| Filter | Meaning |
|---|---|
date:"DD.MM.YYYY HH:mm":"Europe/Berlin" | Date and time: iso (default), unix, unix_ms, rfc2822 or a pattern of YYYY YY MM DD HH mm ss Z ZZ. The time zone is optional; without it the plant's time zone is used. |
number:1:de | A number as text with the given decimals (default 2) and the separators of en, de, fr, es, it, pt or plain. |
round:1 | Rounds and stays a number (in JSON without quotes). |
kw | Divides by 1,000 or 1,000,000 (W to kW or MW). |
upper | Upper case, lower case, without surrounding spaces. |
truncate:120 | At most n characters. |
default:"—" | This text when the value is empty. |
yesno:"yes":"no" | One text for a set value, another for an empty one. |
json | The value as JSON text — objects and lists included. |
Formats and escaping
The content type of a template decides how a value is inserted, so a plant name with quotes or an ampersand never breaks the result:
- JSON — inside a string (
"plant": "{{plant.name}}") a value is escaped as text; outside one ("value": {{alert.value}}) it becomes a JSON value: a number stays a number, text gets quotes, an empty value becomesnull, objects and lists are written as JSON. - XML and HTML —
<,>,&and quotes are escaped. - CSV — a field is put in quotes when it contains the separator, a quote or a line break; in a field the template already quotes, quotes are doubled. The separator is the one your template uses (comma, semicolon, tab).
- Form data — values are URL-encoded.
- Plain text — as it is.
Header values and the email subject never contain a line break. A template is checked when you save it: it must be complete (every section closed, every filter known), at most 64 KiB, and its result for the sample alert must be valid JSON or well-formed XML for those formats. Headers: at most 30, the names of standard headers only. Content-Type follows the format, and Content-Length, Host and the X-Mirox-* headers are set by Mirox — you cannot override them. Every webhook request remains signed: X-Mirox-Signature is the HMAC-SHA256 of exactly the body your template produced.
Examples
Each example is a starting point you copy and adapt:
- Generic JSON (signed envelope) — The documented Mirox alert envelope — a base for ticket systems and automation.
- Microsoft Teams card — An Adaptive Card for a Teams Workflows webhook, with plant, component and value.
- Slack message — Block Kit message for a Slack incoming webhook, with a button to the alert.
- Discord embed — A coloured embed for a Discord channel webhook (red firing, green resolved).
- XML document — The alert as an XML document, for systems that expect XML.
- CSV row — A header and one data row per alert, comma separated.
- Plain-text email — A compact plain-text email with the key facts, in the Mirox email frame (switch the frame off to send the text alone).
- HTML email — Your own HTML email with a fact table — sent exactly as designed.
- Notice to a direct marketer without the BWE interface (CSV) — One German CSV row per report — start, renewal or end of a turbine's outage — with the turbine's identity, the window, the remaining power and the rule's reason; for a webhook receiver, adapted to the marketer's specification.
- Notice to a direct marketer without the BWE interface (email) — The same report as a German email, for an email receiver — edit it to match what the marketer requires.
Start the webhook examples like any other, then choose the copy for a receiver — the receiver dialog lists only your organization's own templates.
The two outage notices (in German) are templates for a rule that reports outages: they render the group outage — the moment, the turbine's name, id, serial number and plant key, begin, end and the window reported so far, rated and remaining power, reason and comment. They serve a marketer without the BWE interface, reached by a webhook or email receiver, and your own mailbox while you rehearse a rule before the marketer's receiver is attached. There is no binding format for such a notice; adapt the columns and the wording to what your direct marketer requires and fill in the MaStR number and the market location as fixed text.
A template for a ticket system that expects XML:
<ticket priority="{{alert.level}}">
<title>{{alert.title}}</title>
<site id="{{plant.uid}}">{{plant.name}}</site>
{{#component.name}}<asset>{{component.name}}</asset>{{/component.name}}
<opened>{{alert.since|date:"iso"}}</opened>
<link>{{alert.link}}</link>
</ticket>
Test Your Alerting
A test run shows the whole path of an alert on one of your plants — without waiting for a real problem and without touching the plant's own data. Open Alert Manager ▸ Overview and click Test alerting Open in Mirox, then choose the plant, the level the test alert should have (up to Critical) and, optionally, receivers.
The platform then writes a scripted test signal for that plant: quiet for 5 minutes, over its threshold for 15 minutes, quiet again. The plant's agent evaluates it like any of your rules, so:
- about 5–10 minutes after the start the test alert opens — at the level you chose;
- only the person who started the run is notified — in the app, by push and by email, according to their own settings — and the chosen receivers get it too; nobody else in the organization is paged;
- about 15 minutes later it resolves by itself, with its resolution notice.
The page follows the run step by step and names who started it. A run ends by itself after about 30 minutes, or earlier with Stop; its alert stays in the history. Test runs never appear among your rules, and test data is only written while a run is active. Admins and Moderators start test runs; up to three may run at the same time.