Overview
The Overview screen shows a daily digest, a summary of your resources and spend, three quick checks, and insight cards that hand off to the copilot.
Overview is the at-a-glance page of emma AI Console: how many resources you run and how healthy they are, what they cost, what needs attention, and where to look next. Almost everything on it can hand off to the copilot. Click a number, an alert, or a card button, and emma opens the chat with a matching question already asked.
Page navigation — click Overview in the left navigation.
In a nutshell:
- A daily digest plus the alerts that need attention
- A summary of resources, health, and monthly cost
- Three quick checks: Scan Infrastructure, Check Drift, Coverage Report
- Insight cards for cost, security, reliability, observability, and more
The tabs under the page heading scope the page to one project, or to All of them. The refresh control on the right reloads the data.
Daily digest
A one-paragraph status: how many resources are healthy, the estimated monthly cost across providers, and how many alerts are unresolved. The refresh icon rebuilds the digest, and Deep dive asks the copilot for a detailed status and optimization opportunities.
Next to the digest are your unacknowledged alerts, most severe first. Filter them by critical or warning, or click one to ask emma about it. With no active alerts, the panel says All systems healthy - no active alerts.
Summary
- Resources tracked, Multi-cloud reach (how many providers you use), and Last scan (when the data was last refreshed)
- A health bar that splits resources into running, busy, stopped, and failed
- Monthly cost with a 30-day trend, broken down by provider and by service
View health breakdown opens counts per resource type (VMs, spot, Kubernetes workers, GPUs, volumes, security groups) and lists the resources that are stopped or failed. Ask emma at the bottom of that dialog continues in the chat.
Quick checks
| Check | What happens |
|---|---|
| Scan Infrastructure | Asks the copilot to discover your resources, check security, and find optimization opportunities. The answer arrives in the chat. |
| Check Drift | Runs right away and shows the result in a dialog: what was added, removed, or modified since the last check, and the change in monthly cost. |
| Coverage Report | Runs right away and grades how much of your infrastructure emma manages, from A+ to F, with managed, unmanaged, and total counts. |
Check Drift rescans the resources in your emma projects (VMs, spot instances, Kubernetes clusters, volumes, security groups, subnets) and compares them against a stored snapshot. The first run has nothing to compare against, so it only records a baseline. Every later run compares against the previous check and then becomes the new baseline, so each result shows only what changed since the last time you clicked.
Drift is checked when you click Check Drift or ask the copilot. Don't count on emma checking for drift in the background.
Do next
If you have no resources yet, this section walks you through a first deployment. Once you do, it offers a New Deploy shortcut that starts a deployment in the chat.
Insights
Each insight card opens a dialog with detail, and the buttons inside hand off to the copilot.
| Card | What it covers |
|---|---|
| Cost & Optimization | Monthly spend by provider, with shortcuts to compare provider pricing and find savings |
| Security & Compliance | Findings by severity, a compliance snapshot, and the posture of your cloud credentials |
| Reliability | Scan and deploy success over 7 days, drift events and incidents over 30 days, recent failures, and your SLOs |
| Observability | Which observability vendors are connected (Grafana, Datadog, New Relic, OpenTelemetry, Prometheus) |
| Multi-cloud reach | Your mix of providers and regions |
| Capabilities | The AI tools available and the IaC formats you can export to |
| Brownfield & Adoption | Resources that exist outside emma deployments, imports by source, and stale or missing scans |
| Managed Services Depth | Which managed-service categories you use, including inference |
Under Reliability, each SLO shows how much error budget is left and how fast it's burning over the last 1, 6, 24, and 72 hours, with an estimate of when the budget runs out at the current rate. + New SLO starts setting one up in the chat.
The footer shows how many of the Slack, Telegram, and GitHub integrations are available, and Manage integrations takes you to Settings → Integrations.
What's next
- The copilot — where every Overview hand-off lands
- InfraMap — the same resources as a live diagram
- Import existing infrastructure — raise your coverage grade
- Optimize your cloud spend — act on what the cost card shows
Last updated on 24 Sept 2026