DOCS-1724 - Document Monitor Creation Agent in Mobot#6871
Conversation
Add a new Create Monitors with Mobot page under Monitors, register the Monitor Creation Agent as a third agent in the Mobot page, wire the sidebar and a cross-link from create-monitor, and add a service release note. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Hi @JV0812 , apologies - this failed the merge window check because sidebars.ts was accidentally omitted from the whitelist. Have a PR now to fix it, and then we can sync this w/main to confirm it passes the check. |
| - If your organization has one connection, the agent adds it automatically. | ||
| - If your organization has more than one connection, the agent lists them and asks which to use. | ||
| 1. When the configuration looks right, the agent shows a confirmation card. Confirm to create the monitor.<br/>{/* TODO: add screenshot of the confirmation card */} | ||
| 1. The agent creates the monitor and returns its ID along with the configured conditions. |
There was a problem hiding this comment.
Along with this mobot shows a chip artifact. Currently on clicking on that user will be redirected to the created monitor. Todo: on clicking on that user will get preview on made on same screen.
Reference Thread
There was a problem hiding this comment.
Added to the create steps: the agent returns the monitor ID and Mobot displays a chip for the new monitor, which you can click to open the created monitor. I documented only the current behavior (click opens the monitor) and left out the in-screen preview since that's a future TODO. — via Claude Code
|
|
||
| The new monitor appears on the **Monitors** tab, the same as a monitor created through the form. | ||
|
|
||
| ## Update a monitor in the conversation |
There was a problem hiding this comment.
only these field can be updated
- name
- description
- queries
- triggers
- notifications
- queryTimeType
There was a problem hiding this comment.
Scoped the update section to exactly these fields: Name, Description, Query, Trigger conditions, Notifications, and Query time range (queryTimeType). — via Claude Code
GEO: add at-a-glance intro, question/how-to headings, and an FAQ. Review fixes: document the post-creation chip, scope updatable fields (name, description, query, triggers, notifications, query time range), and note the agent cannot disable or delete a monitor. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kimsauce
requested review from
margaret-selid and
tp-sl
and removed request for
priyanshbarya-sumo
There was a problem hiding this comment.
Hi @JV0812 , per Chitransh, it looks like this should be positioned more as a skill/functionality rather than a selectable agent.
@priyanshbarya-sumo , I just viewed your demo and it looks like there won't be a button called Monitor Creation Agent - it's a functionality you can call on - is that right?
@tp-sl Since Mobot v2 is going GA end of the month, can you please confirm the wording?
3 participants
Purpose of this pull request
This pull request documents the new Monitor Creation Agent in Mobot, which lets you create and update logs monitors from plain-language prompts.
Changes:
docs/alerts/monitors/create-monitor-with-mobot.md— supported monitor types (Logs only), detection types (Static, Anomaly, Outlier), fields the agent configures, the conversational create/update walkthrough, and example prompts.docs/search/mobot.md— registers the Monitor Creation Agent as a third agent (intro, At a glance, Getting started table) and adds a dedicated section linking to the new page.sidebars.ts— adds the new page to the Monitors category.docs/alerts/monitors/create-monitor.md— cross-reference tip.blog-service/2026-07-10-search.md— service release note.Open items before merge (SME confirmation)
{/* TODO */}in the new page.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1724