Day 2 Ops
The same platform—conversation, IDE, and API
AI Copilot for Day 2 Ops sits on top of Exemplar's service catalog, integrations, and Context Lake. Ask questions, draft automations, and invoke allowed actions with guardrails—whether you are in the console, your editor via MCP, or a script calling APIs.
How it connects
IDE and MCP clients use the same tools as the dashboard
Monitoring, catalog, and webhooks surface as tools—one policy surface for chat and MCP.
Natural language on top of real tools
Ask in plain language; the copilot maps intent to catalog queries, runbooks, webhooks, and platform APIs—so you are not memorizing twenty URLs.
Grounded in the catalog & Context Lake
Answers tie back to services, owners, dependencies, and live signals from integrations—not a generic model guessing about your stack.
MCP in the IDE
Expose the same actions to Cursor, Claude, and other MCP clients: one governance model whether you click in the console or type in the editor.
Guardrails by design
Sensitive actions stay behind approvals, policies, and audit trails. The copilot suggests and executes within the boundaries your platform team defines.
Where teams use it
Illustrative scenarios—actual behavior depends on your integrations and policies
Service discovery & ownership
Find workloads, who owns them, and what depends on what—without opening five tools.
- Search by team, tier, repo, or runtime
- Surface dependencies before a risky change
- Jump from question to catalog entities
Q: Who owns checkout in prod and what did we deploy last week?
A: Illustrative: the copilot resolves checkout to the owning squad, linked services, and recent deploy events from your connected CI and catalog.
Incidents & triage
Shorten time-to-context when something breaks: symptoms, recent changes, and owners in one thread.
- Correlate alerts with services and deploys
- Suggested checks grounded in your graph
- Hand off to runbooks or automation when ready
Q: Errors spiked on billing-api—what changed?
A: Illustrative: summarize recent deploys, dependency shifts, and linked incidents using catalog and observability data you have connected.
Automation & Day 2 actions
Describe the outcome; wire webhooks, notifications, or self-service actions with review where needed.
- Create or refine webhook flows
- Trigger approved actions against services
- Keep an audit trail for compliance
Q: Notify the platform channel when a prod deploy fails.
A: Illustrative: draft a failure hook to your collaboration tool with retries and signing—subject to your org’s automation policies.
Ways to connect
Pick the surface that matches the workflow
Console chat
Built-in assistant in the Exemplar dashboard for operators and developers.
- Session context inside the product
- Rich replies with links to entities
- Same auth and roles as the console
MCP
Model Context Protocol for AI clients that support tools—Cursor, Claude Desktop, and compatible IDEs.
- Tool calls with your tenant context
- Pair with org-approved clients
- Extends catalog and Day 2 actions to the editor
APIs & automation
Programmatic access for scripts, CI, and advanced integrations where chat is not enough.
- REST and automation-friendly surfaces
- Use in pipelines with service tokens
- Compose with webhooks and catalog APIs
Capabilities
What the copilot helps with
One short example per area—rollout and tooling vary by tenant.
Natural language interface
Turn questions into catalog lookups, summaries, and next steps—without switching context constantly.
You: Which services still run Node 18?
Copilot: Illustrative: returns candidates from catalog metadata and ownership so upgrade campaigns have an assignee per row.
Recommendations
Suggestions for cost, risk, and hygiene—scoped to what Exemplar can see from integrations and policies.
You: Where should we tighten IAM first?
Copilot: Illustrative: prioritizes findings linked to production paths and teams—your security tools and rules still govern enforcement.
Workflow help
Describe automations in prose; get structured steps, configs, or handoffs to operators for approval.
You: Back up stateful data before the database migration window.
Copilot: Illustrative: outlines checks, scheduling, and notifications aligned with webhooks and automation you have enabled.
Context-aware assistance
Uses the service or incident you are in—so answers are specific, not generic platform advice.
You: I am on payment-service—what should I know before this release?
Copilot: Illustrative: summarizes owners, dependencies, recent changes, and policy notes from the graph around that entity.
At a glance
Tools
Catalog, SRE, automation, webhooks—via MCP and chat
Context
Grounded in your graph and integrations
Guardrails
Policies, approvals, and auditability
Get started
Open the console to explore the platform—service catalog, integrations, and AI Copilot capabilities.