Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The source code of most frontend web applications delivered to the browser are typically in a minified form which impacts how stacktraces appear on RUM error events. If this is the case for the web application that you are instrumenting with kloudfuse RUM you will need to configure and set up upload of sourcemaps.

There are two parts to this:

  1. Configure sourcemap storage for the Kloudfuse installation

  2. Configure your web applications build step to automatically upload sourcemaps

Step 1: Configure sourcemap storage for the Kloudfuse installation

Configure your kloudfuse platform as shown in the example below and uncomment the relevant section while replacing the appropriate configuration to match your environment depending on your cloud storage provider. The configuration has similar requirements to how the sessionReplayStorage section is configured (see the Enable RUM on Customer’s Kloudfuse installation page):

global:
  rum:
    sourcemapStorage:
      # type: s3
      # useSecret: true
      # secretName: "kfuse-rum-s3"
      # s3:
      #   region: us-west-2
      #   bucket: rum-sourcemaps
      
      # type: azure
      # useSecret: true
      # secretName: "kfuse-rum-azure"
      # azure:
      #   container: rum-sourcemaps

      # type: gcs
      # useSecret: true
      # secretName: "kfuse-rum-gcs"
      # gcs:
      #   bucket: rum-sourcemaps

Step 2: Configure upload of sourcemaps to your Kloudfuse installation

TBD

  • No labels