Promote RUM MCP toolset to GA#37810
Conversation
|
Preview links (active after the
|
samcolmanetti
changed the title
This comment has been minimized.
This comment has been minimized.
estherk15
left a comment
estherk15
left a comment
There was a problem hiding this comment.
Left one minor suggestion, but it doesn't block this PR!
| ### `search_datadog_rum_events` | ||
| *Toolset: **core***\ | ||
| *Permissions Required: `RUM Apps Read`*\ | ||
| Search Datadog RUM events using advanced query syntax. | ||
|
|
||
| - Show JavaScript errors and console warnings in RUM. | ||
| - Find pages that are loading slowly (more than 3 seconds). | ||
| - Show recent user interactions on product detail pages. | ||
|
|
||
| ### `aggregate_rum_events` | ||
| *Toolset: **core***\ | ||
| *Permissions Required: `RUM Apps Read`*\ | ||
| Aggregates RUM events to compute counts, sums, averages, min, max, cardinality, and percentiles, with grouping support. Use this for statistical analysis and trend data, not for inspecting individual events. | ||
|
|
||
| - Count JavaScript errors by page in the last 24 hours. | ||
| - Show me the p95 loading time grouped by country for my main RUM application. | ||
| - How many sessions had a Core Web Vitals failure this week? | ||
|
|
There was a problem hiding this comment.
We should add the rum toolset next to **core**
Also, as get_datadog_dashboard and upsert_datadog_dashboard, should we move the two core/rum overlapping tools to the beginning of the RUM section, instead of buried inside Core ?
There was a problem hiding this comment.
i updated to add rum to the list of toolsets on the search and aggregate tools in core. i ended up leaving them under the core section so customers can more easily see what the default tools are. don't feel strongly about it. @qsellem let me know if you have a preference.
samcolmanetti
force-pushed
the
sam.colmanetti/rum-mcp-docs-ga
branch
from
a82d766 to
f878849
Compare
- Remove Preview alert from the RUM toolset section in tools.md - Add upsert_rum_metric and delete_rum_metric to the RUM toolset section - Add aggregate_rum_events to the core toolset section - Move rum from Preview toolsets to Available toolsets in setup.md
Use rum.<event_type>.<description> naming convention; hyphens are not valid in RUM metric IDs.
Replace page view count example (covered by OOTB metrics and Product Analytics) with LCP distribution and checkout error examples that reflect the intended alerting/monitoring purpose of custom metrics.
samcolmanetti
force-pushed
the
sam.colmanetti/rum-mcp-docs-ga
branch
from
055bf95 to
83867c9
Compare
5 participants
What does this PR do? What is the motivation?
Promotes the
rumtoolset from Preview to GA in the MCP Server documentation:rumfrom the Preview toolsets section to GA insetup.md## RUMsection totools.mddocumentingupsert_rum_metricanddelete_rum_metricaggregate_rum_eventstotools.mdand labels bothsearch_datadog_rum_eventsandaggregate_rum_eventswith thecoreandrumtoolsetsappend_new_rum_retention_filter,update_rum_retention_filter,reorder_rum_retention_filters, anddelete_rum_retention_filterrumtoolset summary insetup.mdto reflect that retention filters are now manageable, not just readablerum.<event_type>.<description>) in all examplesMerge instructions
Merge readiness:
Additional notes