Operations
Once your software is running in the cloud, this is where you keep an eye on it. Under Workspace → Operation you get four screens: Monitoring, Incidents, Costs, and Security. Monitoring shows the current health of your infrastructure. Incidents is where problems that need attention show up and get triaged. Costs and Security run recurring, automated reviews of your cloud account and hand you a plain-language report.
This section really only applies to cloud-hosted apps. It needs a connected cloud account and discovered infrastructure. Without one, there are no resources to monitor and no cost or security data to review.
In this section
- Monitoring: the resource health dashboard: stat tiles, the Resource health list, and the embedded Incidents tab.
- Incidents: the incident list and detail view, covering tabs, search, the severity filter, incident cards, badges, agent analysis, Create issue / Open issue, and Discuss in chat.
- Costs: recurring, automated reviews of your cloud spend, plus creating a schedule and reading its run history and reports.
- Security: recurring, automated reviews of your cloud security posture, plus creating a schedule and reading its run history and reports.
Costs and Security use the same underlying screens and only differ in wording and presets. Read whichever one matches what you are setting up; the mechanics are the same.
Where to find it
All four screens live under Workspace → Operation in the left sidebar, scoped to whichever project is currently selected:
- Monitoring:
/operation/monitoring - Incidents:
/operation/incidents - Costs:
/operation/costs - Security:
/operation/security
Who can do this?
| Screen | To view | To manage (create, pause, run, delete) |
|---|---|---|
| Monitoring: Resource health | monitoring:read | Read-only screen |
| Monitoring: Incidents tab | incident:read (tab hidden without it) | Read-only |
| Incidents (list and detail) | incident:read | incident:manage (Create issue, and so on) |
| Costs | cost:read | monitoring:manage and cost:read |
| Security | security:read | security:manage |
How this connects to the rest of the platform
- Incidents are never created by hand. They appear automatically from a failed health check, an alert from a connected tool, or a signal from your deployment pipeline. See Incident detail for how ACE groups repeats, flags flapping, and settles a resolved incident after a grace period.
- Turning a finding into work. On an incident, click Create issue (or Open issue if one already exists) to start a fix, which dispatches an agent immediately. On a finished Costs or Security report, you can likewise create a linked card, or use Discuss in chat to ask follow-up questions first. Either way, a person always decides to turn a finding into work; nothing here fixes itself automatically.
- Cost and Security schedules need a connected cloud account for the agent to actually inspect. A connected Slack or Teams channel lets reports and incident notifications reach chat directly; without one, they still land in the in-app inbox.