rum
RUM Querying Skill
Query and analyze Coralogix Real User Monitoring data using the cx logs command with DataPrime syntax.
Understanding RUM in Coralogix
RUM captures real user interactions from browsers and mobile apps — errors, performance metrics, network requests, web vitals, and user interactions. RUM data is stored as regular logs in the cx_rum subsystem, queried with the same cx logs command and DataPrime syntax used for any other logs.
This means:
- Metadata (
$m.*) and labels ($l.*) work the same as regular logs — you can filter on timestamp, severity, etc. - User data (
$d.cx_rum.*) contains all RUM-specific fields — event types, errors, sessions, web vitals, interactions, and more. See the RUM Fields Reference for the complete field catalog. - Session replay and session flows are not available — only individual RUM log events can be queried.
For general log querying concepts and field discovery, see the query-logs skill. For DataPrime query language syntax, see the dataprime skill.
CLI Command
More from coralogix/cx-cli
cx-telemetry-querying
|
176cx-alerts
This skill should be used when the user asks to "manage alerts", "create alert", "list alerts", "check alert status", "enable alert", "disable alert", "investigate firing alerts", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.
159cx-create-dashboard
>
150cx-observability-setup
>
149cx-incident-management
>
147cx-cost-optimization
>
141