Skip to main content
skill CX Codex

cx-rum-setup — Claude Code skill: set up Coralogix RUM

cx-rum-setup is a Claude Code skill that automates Coralogix Real User Monitoring setup for browser and mobile apps.

Apache-2.0 1,300 installs ★ 243 updated 2026-11-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add coralogix/cx-cli --skill cx-rum-setup -a claude-code
Open on GitHub

What cx-rum-setup does

Runs in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. It detects your app's platform—React, Vue, Angular, Next.js, Flutter, React Native, or native iOS/Android—and handles five steps: inspects the repo, picks a Coralogix profile, creates or reuses a RUM key with SendRUMData rights, fetches current SDK docs, and generates init code with the correct coralogixDomain.

Under the hood, it runs cx iam api-keys, cx docs, and cx dataprime commands to manage keys and verify data. The key is created with only rum-ingress:SendData permission—public by design, safe to embed in client code. If multiple Coralogix profiles exist, you'll pick the right team before key operations.

Setup finishes with a query to rum.events to confirm monitoring data is arriving.

What it helps with

  • set up Real User Monitoring on a browser application
  • create a public RUM API key for client-side code
  • generate CoralogixRum.init code with the correct domain
  • verify RUM events are being sent to the server
  • add the RUM SDK to React, Next.js, Vue, Angular, Flutter or a mobile app

Example prompts for the agent

  • Add Coralogix RUM to my React app
  • Set up Real User Monitoring for this Next.js project
  • Create a RUM key and initialize the SDK for my mobile application

How to install cx-rum-setup

1Skills CLI (Vercel)

npx skills add coralogix/cx-cli --skill cx-rum-setup -a claude-code

2Manually: put the files in place

~/.claude/skills/cx-rum-setup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cx-rum-setup/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cx-rum-setup

How do I install cx-rum-setup?

Installation depends on your IDE. For Claude Code, run npx skills add coralogix/cx-cli --skill cx-rum-setup -a claude-code and open ~/.claude/skills/cx-rum-setup/SKILL.md. For Cursor: npx skills add coralogix/cx-cli --skill cx-rum-setup -a cursor, then check .cursor/skills/cx-rum-setup/SKILL.md. For GitHub Copilot, use gh skill install coralogix/cx-cli cx-rum-setup and refer to .github/skills/cx-rum-setup/SKILL.md.

What does cx-rum-setup do?

It automates RUM setup: detects your app's platform (browser, React Native, Flutter, iOS, Android), creates or reuses a public RUM key, installs the SDK, generates init code, and confirms events are reaching the monitoring backend.

What permissions do I need to create a RUM key?

You need DATA-INGEST-API-KEYS:READCONFIG (to list keys) and DATA-INGEST-API-KEYS:MANAGE (to create). If you lack these, ask your admin to create the key in Settings → API Keys, type "Send Your Data Key", preset SendRUMData only.

Source text

SKILL.md · Apache-2.0
---
name: cx-rum-setup
description: >
  Use this skill when the user asks to "add RUM", "set up RUM", "install the RUM SDK",
  "add Coralogix RUM to my app", "create a RUM API key", "RUM public key",
  "init Coralogix RUM", "CoralogixRum.init", "add the browser SDK", "real user monitoring",
  "frontend monitoring", "monitor my web app", "session replay", "track frontend errors",
  "add RUM to React", "add RUM to Next.js", "add RUM to my mobile app",
  or wants to instrument a browser or mobile application with Coralogix Real User Monitoring
  end to end - RUM API key, SDK install, init code, and verifying data arrives.
metadata:
  version: "0.1.1"
---

# RUM Setup Skill

Use this skill to onboard an application to Coralogix Real User Monitoring (RUM): get a RUM API key, install the platform SDK, add the `init` call, and verify events land in the `rum.events` dataset.

---

## CLI Commands

| Command | Purpose |
|---|---|
| `cx iam api-keys list -o json` | List candidate keys and the team ID (no permissions in output) |
| `cx iam api-keys send-data-keys -o json` | List ingest-only keys with their `presets` (RUM keys show `SendRUMData`) |
| `cx iam api-keys get <id> -o json` | Read a key's permissions (`keyInfo.keyPermissions`) and value |
| `cx iam api-keys create --from-file <file>` | Create the RUM key (write - needs approval + `--yes`) |
| `cx docs search <query>` / `cx docs fetch <suffix>` | Current SDK install and init docs per platform |
| `cx dataprime query --source rum.events '<query>'` | Verify RUM events arrive |
| `cx profiles list` | Profiles and regions - pick the active one for both key and `coralogixDomain` |

`cx iam` and `cx dataprime` take `-p <profile>` to target a specific team. `cx profiles` and `cx docs` are local commands - they take no `-p` (`cx profiles list -p ...` is an error).

---

## Workflow

### 1. Detect the platform

Inspect the user's repo before anything else. Signals overlap (React Native apps also list `react`; Flutter and React Native repos contain `ios/` and `android/` folders), so check **in this order and stop at the first match**:

| # | Signal | Platform |
|---|---|---|
| 1 | `pubspec.yaml` | Flutter SDK - ignore its `ios/` / `android/` folders |
| 2 | `package.json` with `react-native` (or `expo`) | React Native SDK - ignore `react` and native folders |
| 3 | `package.json` with `next` | Next.js (browser SDK, client-only init) |
| 4 | `package.json` with a browser signal - `react-dom`, `vue`, `@angular/core`, `svelte`, a browser bundler (`vite`, `webpack`, `parcel`), or an `index.html` entry | Browser SDK (`@coralogix/browser`) |
| 5 | `Podfile` / `Package.swift` / `*.xcodeproj` | iOS SDK |
| 6 | `build.gradle(.kts)` with Android plugin | Android SDK |

A `package.json` alone (Node backend, tooling) is **not** a browser app. If nothing matches, tell the user no supported client app was found instead of guessing.

### 2. Pick the profile - before any key operation

The key and the SDK domain must come from **one profile**, so settle it before touching keys. The active profile is `-p <name>` if given, else `$CX_PROFILE` if set, else the `DEFAULT` row of `cx profiles list` - don't just read the `DEFAULT` row. If there are several profiles and none was named, **ask the user which team the app belongs to now**, then pass `-p <name>` to every `cx iam` and `cx dataprime` call that follows.

`coralogixDomain` is that profile's `REGION` in upper case: `EU1`, `EU2`, `US1`, `US2`, `US3`, `AP1`, `AP2`, `AP3`.

### 3. Get a RUM API key

RUM keys are **public by design** - they ship inside client code. Create it with the **`SendRUMData` preset** - the same key the UI's RUM flow creates. That preset grants exactly one permission, `rum-ingress:SendData`, and is standalone: never add other presets or permissions. (Granting `rum-ingress:SendData` directly also works but shows as a `CUSTOM` key in the UI, so prefer the preset.) In Settings → API Keys a RUM key shows type "Send Your Data" with preset `SendRUMData`. Do **not** pick the `SendData` preset - it grants logs/metrics/spans ingest but not RUM, and makes the key secret, not public.

**Reuse first.** Check for an existing RUM key:

```bash
cx iam api-keys send-data-keys -p <profile> -o json
```

It lists only ingest-only keys, with their `presets`; never reuse a key based on its name. A row with `presets: ["SendRUMData"]`, `active: "yes"` and `hashed: false` is reusable as is, and its `value` is the key. A row with empty `presets` may be a custom RUM key: run `cx iam api-keys get <id> -p <profile> -o json` and reuse it only if it is **active** (`keyInfo.active: true`) **and** `keyInfo.keyPermissions` has `SendRUMData` as its only preset and no other permissions (or `rum-ingress:SendData` as its only permission). Skip inactive keys - the SDK can't send with them. The value is in `keyInfo.value` (returned for unhashed keys - a hashed key can't be reused, create a new one).

**Create one if none exists.** This is a write - describe it to the user and get approval before passing `--yes` (same rules as `cx-platform-admin`).

```bash
cat > rum-key.json <<'EOF'
{
  "name": "<app-name> RUM",
  "owner": { "teamId": <team-id> },
  "keyPermissions": { "presets": ["SendRUMData"], "permissions": [] },
  "hashed": false
}
EOF
cx iam api-keys create --from-file rum-key.json -p <profile> --yes -o json
```

- `teamId`: read `cached_team_id` from the step-2 profile's file `~/.cx/profiles/<profile>.toml` (written by `cx init`), or the `owner.teamId` of any key in `cx iam api-keys list -o json`, or ask the user.
- `Permission denied`: RUM keys are Send-Your-Data (data-ingest) keys, so they need the `DATA-INGEST-API-KEYS` permissions, not the team custom-key ones:
  - `send-data-keys` warns `could not fetch legacy send-data keys` → the role lacks `DATA-INGEST-API-KEYS:READCONFIG` (view keys); keys from the regular list are still shown;
  - on `get` or `create` → the role lacks `DATA-INGEST-API-KEYS:MANAGE` (`get` needs it too, since it returns the key value).

  Don't retry with other payloads. Tell the user which permission is missing and ask them to get it, or to create it in **Settings → API Keys** - key type **Send Your Data Key**, role preset **`SendRUMData`** only (or have an admin do it), then continue from step 4 with the key value.
- `hashed: false` keeps the key value retrievable later - fine for a public RUM key.
- The response contains `value` - that is the `public_key` for the SDK.

### 4. Fetch the current SDK docs

SDK package names, versions, and options change - fetch them instead of guessing (see `coralogix-docs`):

```bash
cx docs search "RUM SDK installation <platform>" --limit 5
cx docs fetch <suffix-from-search>
```

### 5. Install and initialize

Use the profile and `coralogixDomain` from step 2.

Browser example (confirm against the fetched docs):

```bash
npm install @coralogix/browser
```

```ts
import { CoralogixRum } from '@coralogix/browser';

CoralogixRum.init({
  application: '<app-name>',
  environment: 'production',
  public_key: process.env.NEXT_PUBLIC_CX_RUM_KEY!, // or import.meta.env.VITE_CX_RUM_KEY
  coralogixDomain: 'EU1',
  version: '<app-version>',
});
```

Gotchas:

- **Init once, as early as possible** - the app entry point (`main.ts`, `index.tsx`, root layout).
- **Next.js:** init only on the client - a `'use client'` component that calls `init` in `useEffect`, rendered from the root layout. Never in server components.
- **Env vars:** keep the key in env config (`NEXT_PUBLIC_*`, `VITE_*`, `REACT_APP_*`), not hard-coded. It is public, but env config makes rotation easy.
- **`version`** should match the release - source maps and release comparison rely on it.
- **Source maps** (optional) are uploaded with `coralogix-rum-cli` and need a *separate* key - in the UI, key type **Team Key** with role preset **`SourceMapping`** (`source-mapping:ReadMapping` + `UploadMapping`) - never reuse the RUM key, and keep this one secret (CI only, not in client code). See `cx docs fetch user-guides/rum/cli/rum-cli.md` (search doesn't surface it). If the user asks to verify an upload, `cx rum source-maps list --application <app>` confirms the release is there; don't run it unprompted.

### 6. Verify data arrives (optional)

Setup is done once the key exists and `init` is in place - data only flows after the app runs and users hit it, and the SDK sends in batches. Give the user this query to run later, or run it now if they load the app:

```bash
cx dataprime query --source rum.events \
  "filter \$d.version_metadata.app_name == '<app-name>' | limit 10" -p <profile> -o json
```

No rows? Check the browser network tab for requests to the RUM ingress endpoint. Ad blockers, a wrong `coralogixDomain`, or a key with extra permissions are the usual causes.

---

## Key Principles

- **RUM key = `SendRUMData` preset only** - nothing else on the key
- **Reuse before create**, and never pass `--yes` without user approval
- **Fetch SDK docs per platform** with `cx docs` - don't hard-code versions or options from memory
- **Client-side init only**, once, at the app entry point
- **Done = key + init in place** - hand over the `rum.events` query for checking data later

---

## Related Skills

- **`cx-platform-admin`** - general API key management
- **`coralogix-docs`** - fetch platform-specific SDK docs
- **`cx-telemetry-querying`** - query RUM data once it flows

© coralogix · Apache-2.0 · coralogix/cx-cli

Similar skills

All skills for Frontend and UI →

From the same set18

The whole set →
cx-dashboards cx-dashboards is a Claude Code skill that builds and deploys Coralogix dashboards from service metrics, logs, and traces, verifying each query via cx CLI. CX Codex +1 4,400installs cx-platform-admin cx-platform-admin manages Coralogix access controls, API keys, and user roles. Helpful when auditing team permissions or configuring IP access restrictions. CX Codex +1 4,300installs cx-cases Drives Coralogix Cases through the cx cases CLI: assign, acknowledge, resolve, close, re-prioritize, and read the event timeline. CX Codex +1 4,100installs cx-infra Exposes cx infra resources commands for querying Coralogix infrastructure. Runs when you ask about resource health, configuration drift, or raw resource data. CX Codex +1 3,900installs cx-service-catalog cx-service-catalog is a Claude Code skill for querying Coralogix’s Service Catalog and APM metrics. It activates for requests to find entities, inspect their schemas, or examine measurements over time. CX Codex +1 3,700installs cx-slos A skill for Coralogix SLOs: list and inspect targets, check error budget, create and edit definitions through cx slos. CX Codex +1 3,600installs cx-ai-center cx-ai-center is a Claude Code skill that answers questions about your AI apps and agents, including user queries, token costs and guardrails, and manages AI Center configuration. CX Codex +1 3,400installs cx-profiling A Claude Code skill for inspecting Coralogix continuous profiling data via the cx profiling CLI. Identifies services consuming the most CPU or memory down to individual functions. CX Codex +1 1,200installs

Project sponsors

Companies that keep this analytics open