rum

Name: rum
Availability: InStock
Author: Coralogix

Query Coralogix RUM data with cx logs and DataPrime syntax.

114|10|Updated Mar 29, 2026

Search Tags:#logs #web-vitals #frontend-errors #querying #rum #real-user-monitoring

Ready to run

npx skills add https://github.com/coralogix/cx-cli --skill rum

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rum
Source: https://github.com/coralogix/cx-cli/tree/main/skills/rum
Command: npx skills add https://github.com/coralogix/cx-cli --skill rum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Query and analyze Coralogix Real User Monitoring (RUM) data to diagnose frontend performance and reliability issues across web and mobile experiences.

Core Features & Use Cases

Query RUM events using cx logs with DataPrime syntax to filter by event types such as error, web-vitals, network-request, and user-interaction.
Use RUM-specific fields under $d.cx_rum (e.g. event_context, session_context, web_vitals_context) to identify issues, performance bottlenecks, and user experience problems.
Apply the skill to scenarios like debugging slow page loads, pinpointing frontend errors, and understanding user interactions and sessions.

Quick Start

Run cx logs with a RUM-focused query to explore frontend events and vitals.

Frequently Asked Questions about rum

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I query real user monitoring data to investigate frontend errors?▼

Query real user monitoring data by running the cx logs command with DataPrime syntax to filter RUM events by types such as error, web-vitals, and user-interaction. This allows you to pinpoint frontend errors and performance bottlenecks across web and mobile applications.

Can I use DataPrime syntax to filter web vitals and user interaction events?▼

Yes, DataPrime syntax supports filtering Real User Monitoring events by specific types including web-vitals, network-request, and user-interaction. You apply these filters within the cx logs command to isolate and analyze frontend user experience data.

What RUM fields are available for diagnosing slow page loads and session issues?▼

RUM fields are accessible under the $d.cx_rum structure, providing contexts like event_context, session_context, and web_vitals_context. These fields enable you to identify slow page loads, track user interactions, and diagnose session issues.

Does this approach support analyzing both web and mobile user sessions?▼

Yes, Real User Monitoring analysis covers both web and mobile experiences. You can investigate frontend performance, reliability issues, and user interactions across both platforms using the cx logs command with DataPrime syntax.

What is the best way to debug frontend performance bottlenecks using RUM data?▼

Debug frontend performance bottlenecks by querying RUM data with DataPrime syntax to filter web-vitals events. Analyzing the web_vitals_context under $d.cx_rum helps identify specific issues causing slow page loads and poor user experiences.

Why am I not seeing RUM data when querying with the cx logs command?▼

RUM data is filtered by the system metadata field $l.subsystemname == 'cx_rum'. Ensure your DataPrime query includes this subsystem filter alongside the cx logs command to correctly retrieve and analyze frontend events and web vitals.