Understanding the Control Center
How monitors, incidents and notices work together to tell you when something needs attention.
Overview
The Control Center is where your Spojit workspace keeps watch. A monitor checks something on a schedule: whether your workflows are still succeeding, how much of your plan you have used, a page on a supplier's website, a value from one of your APIs, or anything you describe to Miraxa in plain words. When it finds something, it raises an incident or a notice and tells the people and channels you chose.
It sits alongside your workflows rather than inside them. You do not add steps to a workflow to be alerted about it: a monitor watches the workflow's runs from outside. A monitor can also ask Miraxa to investigate each alert and suggest a fix, which you can apply from the alert or let the monitor apply when the risk is low.
Before You Start
- You need a role that can view monitors to open the Control Center. Viewers, Editors, Admins and Owners have it by default.
- Creating and editing monitors needs permission to manage monitors, which Admins and Owners have by default.
Incidents and Notices
Every monitor raises one of two things, and you choose which when you create it.
- Incident - something is wrong, such as runs failing, credits running low, or a value over a limit. An incident stays open until a later check finds things back to normal, and sends reminders while it stays open.
- Notice - something is new, such as a new API version, a price change or a platform broadcast. A notice is told once. You act on it and mark it done, or dismiss it.
The Tabs
- Incidents - what is wrong right now, most serious first, with counts of open incidents at each level.
- Notices - new things to act on, mark done or dismiss.
- Monitors - every monitor, what it watches and how it is doing now. Filter by what it raises, its state or its level.
- Broadcasts - announcements posted for the platform, such as connector API changes.
- Contacts - where alerts go: email addresses, Slack channels and Microsoft Teams channels.
Levels
- Critical - something is broken now.
- Warning - needs attention soon.
- Info - worth knowing; nothing is broken.
The level colours and words a monitor's alerts everywhere and sorts the lists.
An Alert's Page
Open an incident or notice to see its whole story as a timeline: when it was Detected (or Arrived, for a notice), what Miraxa found when it Investigated, the Fix and who applied it, and how an incident ended (Resolved, Closed or Dismissed). Use Copy a summary to paste it into a ticket, or Ask Miraxa about this to talk it through.
Tips
- Start from Recommended for this workspace on the Monitors tab. The recommended monitors cover the problems most teams want to hear about first, such as workflows that stop succeeding and low credits.
- Keep Critical for things that need someone now. If everything is Critical, people stop reading the alerts.
- Use notices for changes you want to know about but that are not failures, so the Incidents tab stays a list of real problems.
Common Pitfalls
- Closing an incident before the problem is dealt with. Closing or dismissing stops its reminders, so nobody hears about it again while it is still wrong.
- Dismissing a notice you meant to act on. Dismissed notices stay under the Dismissed filter if you need them again.
- Creating a monitor with no contacts and not choosing Email me. It still raises incidents and notices in the Control Center, but nobody is told.
Related Articles
- Creating a Monitor
- Applying Suggested Fixes and Using Auto-Apply
- How to Send Monitor Alerts to Slack or Microsoft Teams
- Monitoring Workflow Executions
- Roles and Permissions
- Using Miraxa to Debug and Explain Failed Runs