MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Transformer Stations
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
    • Availability and Maintenance Windows
    • Releases and Versions
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Solar Trackers and Park Controllers
    • Transformer Stations
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Alarm Levels
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Overview
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Generic Modbus Reader
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Security Policy
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • Account Security
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Monitoring & Visualization

    • Real-Time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits and Curtailment
    • Efficiency Detection (PRRC)
    • Local Network Inspector
    • Access Monitoring
    • KPI Dashboard
    • Graph Visualization
  • Data Management

    • Events
    • Alarm Levels and Notifiable Events
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Alert Manager

    • Alert Manager
    • Alert Rules
    • Alerts & Notifications
    • Examples
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN: Address Conflicts
    • Proxy (Web Access to Plant Devices)
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • How Revenue Is Calculated
    • Accounting & Billing
    • Contracts
    • Service Certificates & Invoices
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Temporarily Locked
    • Organization Security Policy
    • Permission System
    • Network Segmentation
    • Cooperation Permission Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
    • Data Isolation

Metrics

Metrics lets your organization define its own key figures. You describe, in one short expression, what should be measured in a single 15-minute interval. The platform does the rest: it applies your expression to each plant, over the period a report covers, and folds the 15-minute values into the figure you want to see.

A metric is defined once for the whole organization and is then available on every plant — you never write a metric "for a plant".

Where to Find It

Metrics belong to the organization, so they live in its glossary on the Data Export page: open Data Export in the main navigation and switch to the Glossary tab. Open in Mirox — Data Export ▸ Glossary. A link to a single metric opens its editor straight away: https://service.mirox.io/#/export?tab=glossary&metric=<uid>.

The Reports page no longer has a metrics tab of its own; chapters still use your metrics through the data picker. Older links to the metrics on the Reports page keep working and lead to the glossary.

  • The organization roles Admin, Moderator, Asset Manager (Technical) and Asset Manager (Commercial) create, duplicate, edit and delete metrics.
  • Every member can see the metrics and use them in reports.
  • A metric marked Private is edited and deleted only by its creator, an Admin or a Moderator. Everyone still sees it and uses it in reports and alert rules, and every author can duplicate it. See Private.

The table shows for every metric its plant types and where it is used; click a row to open the editor. Step-by-step instructions are in Working with Reports.

Defining a Metric

A metric consists of a few descriptive fields and one to four expressions.

New metric creates the metric straight away, and from then on every change is saved as you type — a status chip shows Saving and then Saved, and there is no separate step to confirm. Until its expression validates, the metric is marked Not validated and is never offered as a data source in a report. The moment the expression validates, the mark disappears and the metric can be used everywhere — see Validation.

  • Name, description, unit — how the metric appears in the report data picker and in the finished report.
  • Id — the name templates and chapters use to point at the metric; see Metric id.
  • Expression — what is measured in one 15-minute interval. This is written in MetricsQL, the query language of the platform's time-series store. You write only the per-interval part: the platform adds the plant, the time window and the folding. Never name a plant or an organization in the expression — doing so is rejected, because the same metric has to work on every plant.
  • Fold — how the 15-minute values become one number:
    • Average — the average of the interval values
    • Weighted mean — the average in which each interval counts with the value of a further expression, Weight per slot: Σ(value × weight) ÷ Σ(weight). The weight answers for the whole plant or per the same component as the expression.
    • Sum — the total of the interval values
    • Ratio — the share of expected intervals in which the expression was 1
    • Last value — the value at the end of the bucket
  • Expected (denominator) (optional, for the Ratio fold) — a second expression that decides which intervals count at all, for example "it is daylight". An interval with no expectation is ignored; an interval that was expected but has no measurement counts as not available; a period with no expected interval at all is shown as a dash.
  • Weight (optional) — a static per-component value, such as a component's peak power, used to combine the component values into one plant value. Without a weight, components count equally.
  • Report as — the shape the metric answers in. Plant value gives one number per plant; where the expression works per component, that number is the weighted roll-up described above. Per component gives one column per inverter, combiner box, string or logger, plus the plant value. Duplicate a metric to have the same figure in both shapes.
  • Finest resolution — the finest step a report may print the metric at: 15 minutes, hourly or daily. Coarser steps are always available; choose Day for a figure that only makes sense per day.

A report prints the metric at the resolution its block asks for — 15 minutes, hourly, daily, monthly, or a single value for the whole period — and an export at the step you choose, but never finer than the Finest resolution.

While you type, the editor validates live — syntax, unknown series (with suggestions for what you probably meant), the self-scoping rule, whether the expressions fit the chosen fold, and size. A test run then evaluates the metric on the plant chosen under Evaluate on, and a preview shows a table and a graph with every inverter or component lane and the resulting plant value for a month, quarter or year you pick — a metric reported as a plant value shows that one value alone. Validation and test messages name the plant they were checked against.

Validation

While you type, the editor checks the metric against the plant chosen under Evaluate on at the top of the editor: syntax, unknown series (with suggestions), the self-scoping rule, whether the expressions fit the fold, and size. The verdict lists what is still wrong and shows yesterday's value on that plant, as a report would print it.

As long as a problem remains, the metric is marked Not validated. It is saved all the same, but no report, chapter or export can read it, and the data picker does not offer it. Fix what the editor lists and the mark disappears by itself. Not validated is not the same as a report Draft — a report draft is a finished report waiting to be reviewed and published.

Warnings — a series this plant has not delivered, or a value that looks implausible — do not block the metric; they tell you what to check.

A metric that templates already use and that you edit into a broken state is left out of their reports until it validates again, so keep an eye on the Used in count before larger changes.

Evaluate on only decides where the check, yesterday's sample, the preview, the building blocks and the assistant run. The metric itself belongs to no plant: every report evaluates it on the plant the report is made for.

Metric Id

Every metric has an id: lowercase letters, digits and underscores, at least three characters, not starting with a digit, and unique within your organization. Templates and chapters point at a metric by this id.

You can change the id as long as nothing uses the metric — validated or not. Once a template or a chapter reads it, the id is fixed: the field is locked, and the line beneath it shows where the metric is used. If you really need a new id, take the metric out of those templates and chapters first. If the id you type is already taken, the editor says so and offers to put the stored id back.

The Building Blocks

The editor's side panel lists everything you can build from, so you rarely have to remember a name:

  • Series — the same data as the report's data selection: plant feed-in and production, expected production and reference series, compensation and curtailment, inverters, combiner boxes, strings, battery, weather and infrastructure, each with the labels and steps it carries. Search by name, filter by level, and a mark shows which series the current plant has not delivered yet — the metric still works organization-wide. What a report computes rather than reads (performance ratio, event counts, settlement figures) is listed at the bottom as not expressible, so you know before you write it.
  • Configured values — values from the plant configuration, not measurements: inverter, combiner-box and string DC peak power, plant peak power, the plant inverter capacity, and component counts. They are resolved into the query for each plant when it runs, so an expression uses the name like a constant series — park.inverter.peak_power to weight or threshold per inverter, for example. A plant where no component has the value configured shows an empty preview; the metric itself works on every plant that has them. Two of them are valid per period rather than constant: the plant's effective EEG applicable value — the capacity-weighted anzulegender Wert of the bands in force at that moment — and the Marktwert the plant is settled against, monthly or annual according to its market configuration, both in EUR/MWh. They change over time, and the platform inserts the value in force at each 15-minute slot, so they need no window of their own. A market premium built from the two — clamp_min(park.eeg_value - park.marktwert, 0) — is a blended approximation for reading trends: the settlement prorates every band separately, so it is never the settled figure.

Configured values

Configured values are figures from the plant configuration — peak powers, the inverter limit, component counts and two money values — that you can use inside a metric. Their names start with park., so the name itself shows that the value comes from the plant configuration and not from measured data.

NameMeaningUnitPrevious name
park.inverter.peak_powerDC peak power per inverterWpowerplant_inverter_peak_power
park.gak.peak_powerDC peak power per combiner boxWpowerplant_gak_peak_power
park.string.peak_powerDC peak power per stringWpowerplant_string_peak_power
park.peak_powerPeak power of the plantWpowerplant_park_peak_power
park.inverter_limitInverter limit of the plantWpowerplant_park_limit_inverter
park.inverter_countNumber of inverterscountpowerplant_park_inverter_count
park.string_countNumber of stringscountpowerplant_park_string_count
park.eeg_valueEffective EEG applicable value (anzulegender Wert), valid per periodEUR/MWhpowerplant_park_eeg_value
park.marktwertMarktwert the plant is settled against, valid per periodEUR/MWhmarket_marktwert
  • Read from the configuration, not stored. Configured values are not kept as time series. Each time a metric is computed, Mirox reads them from the plant configuration and inserts them into the query for that plant. The value is therefore always the one configured right now: correct a peak power, and every period computed afterwards — past periods included — uses the corrected value.
  • Computed by Mirox. A metric that uses a configured value is available in reports, in the data export (Metrics tab, CSV and JSON) and through the export API. It is not available through direct access to the time-series database — in your own Grafana dashboards, for example, or any other tool that queries the database itself: the park. names do not exist there. The same holds for the plant value of a per-component metric that is weighted by a configured value — inverters weighted by their peak power, for example — because Mirox computes that roll-up after reading the component values. In the data export these metrics carry a small config badge; hover over it for a short explanation.
  • Weighting by peak power. With a peak power as Weight (for example park.inverter.peak_power), each component counts in proportion to its configured peak power. A component without an entered peak power hardly counts; if no component has one, every component counts equally. Hidden components have no configured value and do not count.
  • Previous names keep working. Metrics saved with the previous names keep working unchanged. New metrics, the editor's building blocks and the assistant use the park. names.
  • Series picked by a plant setting. Some metrics read a series that is in the time-series database, but which one depends on the plant settings — the settled curtailment metrics marked (park's method) read the lane of the settlement method each plant is configured for (Spitz, Spitz light or Pauschal; on a wind plant the wind methods). Their query in the data export shows powerplant_<method>_… with the method left open, and after a preview the tooltip names the method each plant read. With several plants each plant counts with its own method. With direct access to the time-series database you choose the method per plant yourself; to read one method regardless of the settings, pick that method's own metric. In the data export these metrics carry the config badge as well.

Shipped Examples

The Metrics table already holds five metrics that Mirox ships to every organization: Connectivity, Logger availability, Inverter availability in daylight, Sun hours and Feed-in data availability. They carry a lock and an Example badge — they belong to no organization, so they cannot be edited or deleted.

What you can do with them:

  • Open one and read its expressions. They are worked examples of everything described above: the daylight gate, both shapes of the ratio fold, the per-component identity, a unit scale.
  • Click Run preview on the plant you are on, to see the individual lanes and the plant value they add up to.
  • Duplicate one. The copy belongs to your organization, is fully editable, and is the usual starting point for a metric of your own.

The examples are deliberately the simple, transparent version of each question, and every description names what it does not account for. The report's own availability figures — which use the plant's configured logger roster and its settlement methods — stay where they were, under Availability in the report data picker. That is why the examples themselves are not offered in the picker; a duplicate of one is.

Writing Expressions (MetricsQL)

An expression is written in MetricsQL, the query language of the platform's time-series store — the same language the raw metrics behind Grafana are read with. It is evaluated on 15-minute slots for one plant at a time: the platform scopes every series to the plant itself, so an expression never names a plant, a portfolio or an organization. Start from the building blocks the editor offers (the series with their labels, the configured values of the plant, the patterns), let the live validation tell you what is missing, and preview against a plant before saving. MetricsQL is the more capable of the two ways to define a figure: per-component lanes, daylight gating, ratios and folds are all expressible here — metrics are the successor of MiroxQL formulas, the calculated columns of the legacy export, which are no longer edited in the app. The language reference itself is the store vendor's public MetricsQL documentation; the functions and limits the editor accepts are listed in its building blocks. While you type, the editor proposes series names, labels and functions; Tab takes the proposal.

Building on Other Metrics

An expression can use another metric instead of repeating it:

  • metric("<metric id>") — another metric of your organization, by its metric id;
  • series("<series id>") — a platform series as its 15-minute value for the plant, or series("<series id>", "inverter") for one value per inverter (likewise gak, string, …).

A reference stands for the other metric's 15-minute value, before folding: metric("yield") / metric("expected_yield") divides the two values of each interval, and then the fold of this metric applies. A referenced metric can itself use references, up to eight levels deep; a metric that ends up referring to itself is rejected. When a referenced metric changes, every metric built on it follows.

Limits

  • An expression may be up to 4 000 characters; after the platform adds the plant, the store rejects anything longer than 16 KB.
  • A metric may answer with at most 500 series on a single plant.
  • The test run over one day must finish within 5 seconds.
  • Nothing can be measured finer than 15 minutes.

If a metric hits one of these, the editor says so as you type, and the metric stays Not validated until you resolve it.

A Worked Example

Inverter availability (2 % of DC peak) — the share of daylight intervals in which an inverter produced at least 2 % of its DC peak power, weighted by peak power, reported as a percentage with the Ratio fold.

Expression:

max by (inverter_id) (max_over_time(powerplant_inverter_power_ac[900s])) > bool on(inverter_id) 0.02 * park.inverter.peak_power

Expected (which intervals count — there is usable light):

(avg(avg_over_time(powerplant_pyranometer_radiation_power{segment_id!~".+"}[900s])) or avg(avg_over_time(powerplant_weather_radiation_power{segment_id!~".+"}[900s]))) > bool 100

Weight (so large inverters count more in the plant value):

park.inverter.peak_power

Creating a Metric with the Assistant

You do not have to write MetricsQL yourself. The assistant sits inside the metric editor: open New metric — or any metric you are allowed to edit — and it is the chat panel at the top right. It stays quiet until you write to it; nothing is sent before that.

Describe the figure you want in your own words. The assistant already knows the plant chosen under Evaluate on, what you have filled in so far (name, expression, fold, …), the result of the last validation and which series this plant actually writes, so it rarely has to ask the basics. It proposes an expression, a name and a description, validates them and previews them on the plant, and tells you when the platform does not hold the data you asked for or when the query would be too heavy.

A proposal goes into the fields the moment it arrives — the assistant edits with you, and each change is saved as you make it. If you would rather keep what you had, Revert on the proposal in the chat puts the fields back the way they were before it; the proposal stays in the chat and can be applied again. The assistant finishes on its own: a proposal is stored on the metric the moment it is made, so you can send your request, close the page and find the finished metric in the list when you come back. After that it is ordinary editing: change any field, run the preview again, or ask for something different.

The conversation belongs to the metric, not to the browser tab. Close the editor and open the metric again, or reload the page, and the same chat is there beside the fields it wrote.

The chat in the editor takes text only. Photos and documents — the formula page out of a contract, for example — remain a feature of the full chat page; Open in chat carries the conversation over there.

Using a Metric in a Report

In the report editor or the chapter editor, pick the data for a block: your metrics appear in the data picker next to the platform's own items, marked my metric, and behave exactly like them — the same resolutions, the same tables and charts. Because a metric is organization-wide, the same block works unchanged in a report for any plant that has the metric's plant types. A metric marked Not validated is not offered.

Using a Metric in an Alert Rule

A validated metric can be watched by an alert rule of the Alert Manager: the rule judges its value every five minutes on each plant and alerts when it crosses your threshold. Your metrics appear in the rule editor under Your metrics.

Exporting a Metric

A validated metric is part of the metric collection. It can be exported as a time series like every metric Mirox ships, for any plant you can read and over any time range.

Open in Mirox

Data Export ▸ Metrics — click Add metrics. Your organization's metrics are grouped as My Metrics.

What you set on the metric decides how it is exported:

Setting of the metricIn the export
Finest resolutionThe finest step. A metric with 15 minutes offers 15 min, 1 h, day, week, month, quarter and year; one with Day starts at the day. A metric is never exported finer than 15 minutes.
Report as ▸ Plant valueOne column per plant.
Report as ▸ Per componentOne column per component — inverter, combiner box, string, turbine, battery container and so on — like the component metrics Mirox ships.
Fold ▸ Sum with an energy unit (Wh, kWh, MWh)An energy: exported Per interval or as Running total.
Fold ▸ Sum with another unitA counted quantity: exported As measured or as Running total.
Fold ▸ Average, Ratio, Weighted mean, Last valueExported As measured.

With several plants combined into one column, a Sum is added over the plants, an Average is averaged (a power in W, var or VA is added), and a Ratio or Weighted mean is recomputed from the plants' totals. A Last value cannot be combined and is shown per plant.

Three things to know:

  • Not validated means not exportable. The picker shows the metric with the remark Draft — validate it in My Metrics first, and an export link that names it is refused.
  • Money needs the accounting permission. A metric that reads the EEG applicable value or the Marktwert is a money metric. Its column stays empty for plants on which you lack the accounting permission.
  • The id in a link is organization. followed by the metric id, for example organization.inverter_availability_2pct.

The way back works too: Create metric on the Metrics tab of the Data Export page opens this editor without leaving Data Export, and Back to Data Export at its top returns you to the export with the plants, metrics and time range you had. Opened from the glossary, the button reads Back to the glossary. For a figure you need once, without a name or a unit, the export page also takes a raw MetricsQL query; a metric is the right choice as soon as a figure is used again or in a report.

Step-by-step instructions are in Metric Export; the parameters of the links are in the Metric Export API.

Where a Metric Is Used

The Used in column of the metrics table counts the templates and chapters that read a metric — "2 templates · 1 chapter", for example. Click the count to see them by name, each with an Open link: a template opens in the report editor, a chapter in the chapter editor. A template counts whether it reads the metric in a chapter of its own or through a library chapter. Export templates that carry the metric as a column count as a use as well.

While a metric is used:

  • it cannot be deleted — the delete dialog lists the templates and chapters instead of offering Delete; remove the metric from each of them, and from the export templates that carry it, first;
  • its id cannot change — see Metric id;
  • a change to its expression shows in every report generated from those templates afterwards. Reports generated earlier keep their numbers.

A metric that another metric builds on or that an alert rule watches cannot be deleted either; the message names them.

A metric nobody uses can be deleted from the table or from the editor; reports generated earlier keep their numbers. Shipped examples cannot be deleted.

Plant Types

A metric works on the plant types of the series it reads. Mirox works this out — you never set it:

  • turbine and other wind series → Wind
  • battery series → Battery
  • inverter, string, combiner-box and other PV series → Solar
  • series every plant has, such as the feed-in meter, weather or market prices → All plant types

A metric that reads series of several types works on each of them. The editor shows the result beside the verdict (Works on), and the metrics table has a Plant types column. A chapter that uses the metric takes over its plant types, so it only appears in the reports of plants that have one of them — see Plant types. When the plant chosen under Evaluate on has none of the metric's types, the editor says so: the metric answers nothing there, so pick another plant to check it.

What Cannot Be Defined

Some figures are computed by the platform itself and must be taken from the existing items rather than rebuilt:

  • Performance ratio and expected production — use the platform-computed items, which are also available as building blocks.
  • Curtailment settlement — derived from your market and tariff configuration.
  • Per-inverter AC nominal power — not stored per inverter, so it cannot be referenced.

Related Pages

  • Reports — where metrics are used
  • Alert Manager — alert rules on your metrics
  • Working with Reports — step-by-step guide, including creating a metric
  • Reports FAQ — why a metric cannot be deleted or renamed, and more
  • Metric Export — export metrics as time series
  • Metric Export API — the parameters of the export links
  • MiroxQL Formulas — the calculated columns of the legacy export
  • AI Assistant & Wizards — the assistant that also works inside the metric editor
  • Member Permissions — who may create organization metrics
Prev
Reports
© 2026 Mirox Verwaltungs GmbH. All rights reserved. | Privacy Policy