RUM Session Replay Storage: Google GCS

Session replay storage is optional. RUM captures views, actions, errors, and resources without it — add it only if you want to record and replay user sessions. This page covers only the GCS-specific steps; the rest of RUM enablement is in RUM Instructions.

Create a GCS bucket

You can store RUM session recordings in a GCS bucket. Follow these steps to create this bucket, and note the GCS bucket name and the credential (secretKey):

  1. Create a new bucket. See Google Cloud’s documentation on Create buckets.

  2. Create a service account on GCP IAM that has access to the bucket.

  3. Create a new key under this service account. This creates and downloads a credential file.

  4. Rename this local credential file to secretKey.

  5. Note the following for the next steps:

    • GCS Bucket Name

    • Credential file named secretKey

Create Secret for Kloudfuse Namespace

Run the following command in the cluster that runs Kloudfuse. The command uses kfuse, the namespace the standard Helm install uses. If you installed Kloudfuse in a different namespace, use that namespace instead; the secret must be in the same namespace as the Helm release.

Create a Secret for Kloudfuse Namespace
kubectl create secret generic -n kfuse kfuse-rum-gcs --from-file=./secretKey

Add sessionReplayStorage to custom-values.yaml

Merge a sessionReplayStorage block into the global.rum section described in RUM Instructions:

global:
  rum:
    enabled: true
    sessionReplayStorage:
      type: gcs
      useSecret: true
      secretName: kfuse-rum-gcs (1)
      gcs:
        bucket: rum-session-replay (2)
yaml
1 secretName: Secret created in Create Secret for Kloudfuse Namespace.
2 bucket: GCS bucket created for session replay storage, in Create a GCS bucket.

Then complete the remaining steps — Kafka topics, TLS, ingress, log-parser rules, and the UI toggle — in RUM Instructions.