Creating a Monitor

Draft a monitor with Miraxa, start from a recommended one, or build it yourself in the one-sentence editor.

Overview

A monitor checks one thing on a schedule and raises an incident or a notice when it finds something. In Spojit you build it as a single sentence, such as Open an incident when workflows stop succeeding in all active workflows, checking every 15 minutes, and tell Ops in Slack as Warning, where each part of the sentence opens its own settings.

You can describe what you want to Miraxa and let it draft the monitor, start from a recommended monitor, or build it yourself. Whichever you choose, you can test the monitor before saving it.

Before You Start

  • You need permission to manage monitors. Admins and Owners have it by default.
  • If the monitor should alert Slack or Teams, add the channel as a contact first. See the Contacts tab.
  • Your plan sets how many monitors you can have and how often they can check.

Steps

  1. Open Control Center from the main navigation and go to the Monitors tab.
  2. Choose how to start:
    • Type what you want watched under What should Miraxa keep an eye on? and choose Draft it with Miraxa. Miraxa drafts the monitor in a chat. Choose Create monitor to save it as drafted, or Edit first to adjust it.
    • Or choose Set up on a monitor under Recommended for this workspace. It opens in the editor.
    • Or choose New monitor to start blank.
  3. Give it a Name.
  4. Under What should it do when it finds something? choose Tell me once (a notice for each new thing) or Alert me while it's wrong (an incident that stays open until it clears).
  5. Select each highlighted part of the sentence to set it: what it watches, how often it checks, who to tell, and how serious it is.
  6. Open More options to turn on suggested next steps, set incident timing, or start it paused.
  7. Choose Test it now to run one check without saving anything.
  8. Choose Create monitor.

Settings Reference

  • What it watches - the source: workflow runs, usage and credits, a web page, a connection, broadcasts, or a question for Miraxa (Ask Miraxa).
  • Checking - every few minutes or hours, or at set times such as weekdays at 9am.
  • Who to tell - Email me, any of the workspace's contacts, and whether to also tell them when a fix is applied.
  • How serious - Critical, Warning or Info.
  • Only open it if it holds for - waits before opening an incident, so a single blip does not alert.
  • Keep it open after it clears for - stops a flapping problem from opening and closing repeatedly.
  • Remind every - how often to remind people while an incident stays open. One hour by default.
  • Suggested next steps - asks Miraxa to investigate each alert and suggest a fix. Uses AI credits.
  • Start paused - saves the monitor without it checking yet.

Tips

  • Describe the outcome you care about to Miraxa, such as "make sure my orders are going through", rather than the mechanics. It picks the right source and settings, and you can adjust them before saving.
  • Use Test it now on a monitor that watches a web page or a connection to check it reads what you expect.
  • Add a Description saying why the monitor exists and who owns the problem, so the next person knows what to do with an alert.

Common Pitfalls

  • Checking more often than the problem needs. A daily report does not need checking every minute, and monitors that ask Miraxa use AI credits on every check.
  • Watching all workflows when only a few matter. Choose Chosen workflows or Folders, and use Only workflows that are active to skip drafts.
  • Switching between Tell me once and Alert me while it's wrong on a saved monitor. It changes what the monitor watches, so it starts again from its next check.

Related Articles

Learn More

Ready to build this?

Start on the free plan: 500 AI credits a month, no card needed.

Start free

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.