Enable RUM on Kloudfuse for AWS S3

Create Session Replay

You can store RUM session recordings in an AWS S3 container. Follow these steps to create an S3 bucket:

1. Follow instructions in AWS documentation on Creating a bucket.

2. Save for following tasks this information:

   • S3 accessKey and secretKey; use them to create a secret on the Kloudfuse.
   • S3 bucketName and awsRegion where the bucket exists

Create Secret for Kloudfuse Namespace

Run the following command in the cluster that runs Kloudfuse:

Create a Secret for Kloudfuse Namespace

kubectl create secret generic kfuse-rum-s3 --from-literal=accessKey=<accessKey> --from-literal=secretKey='<secretKey>'

Configure the custom-values.yaml File

1. Generate a UUID by running the following command:

uuidgen | tr 'A-Z' 'a-z'

2. Add a global.rum section to the custom-values.yaml file:

     rum:
       enabled: true
       applications:
      - name: kf-frontend
        id: 944f6a58-dbc2-45ad-bf93-def505aaff62

sessionReplayStorage:
      type: s3
      useSecret: true
      secretName: "kfuse-rum-s3"
      s3:
        region: us-west-2
        bucket: rum-session-replay-playground

3. List RUM-specific Kafka topics in the custom-values.yaml file.

    - name: kf_rum_session_replay_topic
      partitions: 3
      replicationFactor: 2
    - name: kf_rum_views_topic
      partitions: 3
      replicationFactor: 2
    - name: kf_rum_actions_topic
      partitions: 3
      replicationFactor: 2
    - name: kf_rum_resources_topic
      partitions: 3
      replicationFactor: 2
    - name: kf_rum_longtasks_topic
      partitions: 3
      replicationFactor: 2
    - name: kf_rum_errors_topic
      partitions: 3
      replicationFactor: 2

4. Specify the TLS configuration in the tls section of the custom-values.yaml file, and ensure you use a public host.

tls:
     enabled: true
     host: playground.kloudfuse.io
     email: admin@kloudfuse.com
     clusterIssuer: playground-letsencrypt-prod

5. Specify the Ingress configuration in the ingress section of the custom-values.yaml file.

ingress:
     controller:
       service:
         external:
           enabled: true
         externalTrafficPolicy: Local

6. Enable RUM in the ingester section of the custom-values.yaml file:

ingester:
     config:
       rum:
         enabled: true
         datadog:
           proxyToDatadogEnabled: false

7. To ingest frontend logs into Kloudfuse, add parsing rules in the log-parser section of the custom-values.yaml file.

      - remap:
          args:
            kf_additional_tags:
              - "$origin"
              - "$application_id"
              - "$session_id"
              - "$view.id"
              - "$view.url"
              - "$view.referrer"
              - "$error.handling"
              - "$error.kind"
              - "$error.stack"
              - "$error.message"
              - "$http.method"
              - "$http.status_code"
              - "$http.url"
          conditions:
            - matcher: "__kf_agent"
              value: "datadog"
              op: "=="

8. Enable RUM in the ui section of the custom-values.yaml file:

ui:
     config:
       rum:
         enabled: true

9. Upgrade the cluster using these changes, and ensure that all pods are active.

Instrument the Frontend Application

To set up the Frontend SDK for RUM, see instructions in RUM Setup.

Here is guide to the parameters to configure for SDK initialization:

• applicationId: '<APPLICATION_ID>'
• clientToken: '<CLIENT_TOKEN>'
• site: '<SITE>'
• proxy: '<KFUSE_RUM_ENDPOINT>'
• service: '<APPLICATION_NAME>'
• env: 'production'
• version: '1.0.0'
• sessionSampleRate: 100
• enableSessionRecording: true
• enableLogCollection: true

Enable Authenticated Ingestion

(Optional)

1. To enable ingestion authentication, set global authConfig to true in the custom-values.yaml file:

global:
     authConfig:
       enabled: true

2. Generate a new authentication token:

uuidgen | tr -d '-' | tr 'A-Z' 'a-z' | sed 's/^/pub/'

3. Configure one or more client tokens in the ingester config rum section of the custom-values.yaml file:

ingester:
     config:
       rum:
         enabled: true
         clientTokens:
        - rumauthkey1: <unique authtoken value>
        - rumauthkey2: <unique authtoken value>

4. Match the generated auth tokens to the clientToken value in the frontend RUM SDK configuration:

kfuseRumSDK.init({
       config: {
           applicationId: '<application id>',
           clientToken: '<unique authtoken value>',
           ...
       }
})