Skip to content
Docs
GitHub

First use and maintenance

Applies toAlpha

Complete Install services, confirm service readiness and have the bootstrap token ready.

  1. Create the first administrator

    Section titled “Create the first administrator”

    Open https://rum.example.com/setup and fill in:

    1. Organization name.
    2. Your display name and work email.
    3. A password of at least 8 characters including an upper-case letter, a lower-case letter and a symbol, and its confirmation.
    4. The Bootstrap Token saved in the credentials step.
    5. Submit the initialization form.

    Helm production deployment does not seed local demo accounts. This entry closes after initialization; use the created account for subsequent logins. If the Instance is already initialized, sign in with an existing administrator account.

    Success: You are signed into the Console and can access your Organization.

  2. Connect the first real Project

    Section titled “Connect the first real Project”

    Follow Create your first project: select the SDK platform, configure the application origin and production Environment, copy the onboarding DSN and initialize the SDK.

    After deploying the application, visit a page and send a test Event. Select the same Project, production and the last 15 minutes in the Console, then find the Event and its Session.

    Success: Telemetry has passed through Ingest, Kafka and Consumer and is queryable. If not, check origin, DSN, Environment and time range before pipeline logs.

Next steps

Section titled “Next steps”

Pick what your Instance needs next. None of it blocks the first events.

Source MapsConfigure OSS or S3-compatible object storage, then upload build artifacts.
Alerts and notificationsAdd a notification channel and alert rules.
Capacity and retentionSet retention, watch storage pressure and Kafka lag, and validate your real load.
Backup and restoreAutomate backups and complete a restore drill.
Upgrades and rollbackKeep configuration, image versions and backups, then follow the supported sequence.

To save notification credentials in the Console instead of the runtime Secret, add OPENRUM_MASTER_KEY to the Secret and set config.managedSecrets.enabled: true. Generate the key with openssl rand -base64 32 and back it up securely. For resources, scaling and network details, see the Kubernetes and Helm reference.

Release Alpha · commit local