Monitoring plan

The monitoring plan analyzes a domain's data and recommends what to monitor. Instead of configuring monitors table by table, you point it at a domain and it ranks and deep-dives the most important assets, then proposes a plan of monitors for you to review and enable. Nothing is deployed until you approve it -- you are the checkpoint at every step.

How it works

The monitoring plan runs scoped to a single domain. When you create a plan, the agent ranks the domain's assets by criticality, deep-dives the highest-priority ones, and proposes a plan of monitors -- each with a plain-language reason for the recommendation. It focuses effort on the assets that matter most rather than monitoring everything.

Recommendations are never deployed automatically. You review the plan and enable all of it, or a subset by database or by monitor. You can also mark up a plan and re-run it: drop a table, drop a database, stop proposing a specific monitor, or add an asset the agent missed.

Deploy in five steps

With your domain in place and data ingestion running, deployment takes minutes of hands-on time.

1. Open the monitoring plan. Navigate to Domains, select your target domain, and open the Monitoring Plan tab.
2. Create the plan and add context. Click Create monitoring plan. When prompted, describe the use case in your own words: business purpose, critical tables, known failure modes. Context measurably improves the agent's accuracy.
3. Let the agent analyze. Generation runs unattended -- it works from historical patterns in your data, with no configuration needed from you during this window. Expect a few hours for most domains, and longer for domains with many qualifying tables: the agent spends up to 1-2 minutes per table, so a large domain can take many hours.
4. Review and enable. Review the proposed monitors -- this is the human checkpoint. Once satisfied, enable the whole plan or a subset.
5. Turn on the operational agents. In the domain's About tab, configure the agents that keep monitoring healthy without manual effort: automated triage on, automated troubleshooting for high and medium priority alerts, and the tuning agent on.

Reviewing and enabling the plan

The plan groups its recommendations by coverage area for the domain and shows an estimated daily credit cost for the whole plan and for each monitor. You stay in control of what actually runs.

• Enable monitors one at a time or all at once. Turn on a single proposed monitor, enable everything in a coverage group, or use Enable all to deploy the entire plan.
• Track each monitor's state. Come back to the plan any time to see the state of every proposed monitor -- staged (proposed, not yet deployed), enabled, paused, or deleted. The plan is a living view of what it recommended and what you have acted on.
• Regenerate the plan. Use Regenerate to have the agent re-analyze the domain and produce a fresh set of recommendations -- for example after you have added assets, defined use cases, or changed the context you gave it.
• Export as YAML. Export the plan as YAML to manage the recommended monitors in Monitors as Code, so they live alongside the rest of your version-controlled configuration.

When you enable a monitor from the plan, it is created by the Agentic Platform Agent user ([email protected]), so you can tell plan-created monitors apart from ones authored by hand. Each of these monitors keeps a View monitoring plan link back to the plan it was built from.

Before building the plan: structure your domain

The agent plans per domain, so domain hygiene is the single biggest lever on plan quality.

• Organize domains with clear logic. Give the domain meaningful boundaries -- medallion layers, application or product lines, or data-mesh ownership. Structure it the way your team already thinks about the data.
• Assign every related asset. Add all related tables, dashboards, and other assets to the domain. Coverage is only as complete as the assets the agent can see.
• Define your use cases. Use cases are generated automatically by Monte Carlo from your tables' usage, queries, and lineage, once that data has been ingested for at least 48 hours. They describe the business purpose of a group of tables and drive which assets the agent prioritizes.
• Enable data sampling. Field-level (validation) recommendations require data sampling. Without it, the plan returns table-level monitors only.

Accessing the monitoring plan

In the Monte Carlo UI

The monitoring plan is available from any domain. Navigate to Domains, open your target domain, and select the Monitoring Plan tab, then click Create monitoring plan.

Access control

The plan runs on the permissions of the user who creates it, so it can only see and plan against assets that user can access.

If something looks off

Security & data privacy

For more detail on security and data privacy, see the AI Features and Technical Information documentation.

Feedback

Have feedback or requests on the monitoring plan? Reach out via our Support Agent.