> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spojit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What a monitor can watch

> Workflow runs, usage and credits, public web pages, your HTTP connections, broadcasts, or anything you ask Miraxa to check.

A monitor's source is what it checks. Which sources you can pick depends on whether the monitor [tells you once or alerts you while something is wrong](https://docs.spojit.com/control-center/monitors.md#tell-me-once-or-alert-me-while-its-wrong).

| Source | Tell me once (notice) | Alert me while it's wrong (incident) |
| - | :-: | :-: |
| [Workflow runs](#workflow-runs) | | ✓ |
| [Usage and credits](#usage-and-credits) | Usage statements | ✓ |
| [Web page](#web-page) | ✓ | ✓ |
| [Connection](#connection) | ✓ | ✓ |
| [New broadcasts](#new-broadcasts) | ✓ | |
| [Ask Miraxa](#ask-miraxa) | ✓ | ✓ |

## Workflow runs

Four sources watch how your workflows are running. Each checks every workflow it watches separately, so one failing workflow opens its own incident.

| Source | Opens an incident when |
| - | - |
| **Stopped succeeding** | A workflow has failed a number of times in a row since it last succeeded. |
| **Failed runs** | A workflow has failed a number of times **over the last** period you choose. |
| **Error rate** | The share of a workflow's finished runs that failed in the period passes your limit. **Judge only with at least** a number of finished runs (5 by default) stops a single failure on a quiet workflow from counting as 100%. |
| **Stuck runs** | A run is still going after the time you set. Runs waiting for an approval do not count. |

Choose which workflows to watch:

* **All workflows**, **Chosen workflows**, or **Folders** (which includes their subfolders and any workflows added to them later).
* **Leave out** specific workflows.
* **Only workflows that are active**, to skip drafts and paused workflows.

Watching all workflows or whole folders needs permission to view every workflow in the workspace.

## Usage and credits

These sources need permission to manage billing.

| Source | What it watches |
| - | - |
| **Low credits** | Your workspace's remaining AI credits. Opens an incident when they drop below your limit. |
| **Usage this month** | How much of a monthly allowance you have used, as a percentage: AI credits, execution minutes or emails. |
| **Overage this month** | Use past your allowance, for AI credits or execution minutes, as a share of your overage budget or in units. |
| **Usage statements** | Tells you once each time a usage statement closes. |

Usage monitors do not count toward your plan's monitor limit.

## Web page

Watches a public page: one that shows its content without JavaScript or a login. Enter its **Address**, and optionally a CSS selector in **Only this part** to watch one section instead of the whole page (a price, a status line, a table).

Choose what to **tell you when**:

| Option | Raises |
| - | - |
| **The text changes** | A notice each time the page's text changes. |
| **Miraxa answers a question yes** | A notice when Miraxa reads the page and answers your question yes, such as *"Has the shipping cut-off for Christmas been announced?"* |
| **A value Miraxa reads from it** | Miraxa reads a named value from the page each check, such as *"the price of the 2kg bag"*. Tell you when it changes, changes by at least a percentage, or passes a comparison (more than, at least, less than, at most, exactly, anything but). A number compared against a limit raises an incident; a change raises a notice. |

Questions and value reads use AI credits on each check.

## Connection

Calls one of your [HTTP connections](https://docs.spojit.com/connectors/utilities/http.md) on each check, using its saved credentials. Set the **Method** (GET or HEAD), the **Path** on the connection's base address, and optional **Headers**. To watch one value in a JSON response, give its **Field** as a JSON path, such as `$.data.rate`.

Each check is a real call to that API, so choose a schedule your API is comfortable with.

| Option | Raises |
| - | - |
| **A number in the field passes a rule** | An incident while the number is over (or under) your limit. |
| **It changes** | A notice each time the response or field changes. |
| **Miraxa answers a question yes** | A notice when Miraxa reads the response and answers yes. |
| **A value Miraxa reads from it** | As for web pages. |

## New broadcasts

Turns platform [broadcasts](https://docs.spojit.com/control-center/access-and-limits.md#broadcasts) into notices. Choose the **Tags** to follow, optionally narrow it with **Only about** (for example, one connector), and optionally add a yes or no question for Miraxa so only the broadcasts that matter to you become notices.

## Ask Miraxa

Say what to watch for in your own words. On each check Miraxa looks with read-only tools and decides whether to alert. For example:

* *"Tell me if any order workflow has not run in the last two hours during business hours."*
* *"Alert me if more than five runs failed for the same reason today."*
* *"Let me know when the supplier's price list page shows a new effective date."*

Miraxa can read your workflows, runs, connections, connectors, monitors and members, and search your knowledge base. Under **More options** you can also let it:

* read up to five **web pages** you list (it reads only those);
* **search the web** (uses extra credits);
* work in your **time zone**, so *today* and *tomorrow* mean what you expect.

Each check uses AI credits. Set **Most credits a check may use** (50 by default) and **Most credits a day** (500 by default) to keep the cost where you want it.

As a notice monitor, it tells you once for each new finding. As an incident monitor, it alerts while the finding holds and again when it clears. Use **Test check** before saving to see what it would decide and what a check costs.

> [card] [Try this on the free plan](https://miraxa.spojit.com/signup)
>
> 500 AI credits and 200 workflow runs a month, no card needed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.