Documentation Grafana Cloud Monitor applications Frontend Observability Source map uploads

Faro JavaScript bundler plugins

A collection of plugins for various JavaScript bundlers. Used in conjunction with the Faro Web SDK to unlock additional features in Grafana Cloud Frontend Observability.

Get started

The Faro JavaScript bundler plugins work with the Faro Web SDK and Grafana Cloud Frontend Observability. To use these bundler plugins, you must first have instrumented your JavaScript application with Faro and be sending your telemetry data to a Faro Collector endpoint in Grafana Cloud. Follow the Frontend Observability quickstart guide to get started.

After you have an instrumented JavaScript application sending data to Grafana Cloud, you are ready to get started.

Installation

To install the Faro JavaScript bundler plugins, use the package manager of your choice.

Webpack

To install the Webpack plugin with npm, run:

bash Copy

npm install --save-dev @grafana/faro-webpack-plugin

To install the Webpack plugin with yarn, run:

bash Copy

yarn add --dev @grafana/faro-webpack-plugin

Rollup/Vite

Rollup and Vite are both supported by the same plugin.

To install the Rollup/Vite plugin with npm, run:

bash Copy

npm install --save-dev @grafana/faro-rollup-plugin

To install the Rollup/Vite plugin with yarn, run:

bash Copy

yarn add --dev @grafana/faro-rollup-plugin

Obtain an API key

In order to use the Faro JavaScript bundler plugins, you need to generate an API key with the necessary permissions to upload source maps to Grafana Cloud. To generate an API key, follow these steps:

1. Navigate to the Grafana website.
2. Sign in to your account and then click the My Account button in the top right corner.
3. In the sidebar under Security, click Access Policies and then click the Create access policy button.
4. After creating your access policy, click the Add token button in the card for your newly created policy.
5. Select the sourcemaps:read, sourcemaps:delete, and sourcemaps:write scopes from the drop-down list.
6. Create the token and be sure to copy the token value, as you aren’t be able to see it again.

After you have generated an API key, you can use it in the Faro JavaScript bundler plugins to upload your source maps to Grafana Cloud. Use the generated API key as the apiKey value in the configuration options for the bundler plugins.

For best practices, store your API key in a secure location and don’t expose it in your source code. Consider using environment variables or a secrets manager to securely store and access your API key.

Usage

Details of how to use the plugins with your bundler reside in the Frontend Observability plugin under the Settings > Source Maps tab after clicking into your instrumented app.

That tab includes the necessary configuration for the Faro JavaScript bundler plugins, including the appName, appId, and endpoint values that you need for the plugins to work with your app. The details provided below are general instructions for how to use the plugins with your bundler.

Webpack

To use the Webpack plugin, add the following to your webpack.config.js:

JavaScript Copy

// other imports
import FaroSourcemapUploaderPlugin from '@grafana/faro-webpack-plugin';

module.exports = {
  // other configs
  plugins: [
    // other plugins
    new FaroSourcemapUploaderPlugin({
      appName: '$your-app-name',
      endpoint: '$your-faro-collector-url',
      apiKey: '$your-api-key',
      appId: '$your-app-id',
      gzipContents: true,
    }),
  ],
};

Rollup/Vite

To use the Rollup/Vite plugin, add the following to your rollup.config.js or vite.config.js:

JavaScript Copy

// other imports
import faroUploader from '@grafana/faro-rollup-plugin';

export default defineConfig(({ mode }) => {
  return {
    // other configs
    plugins: [
      // other plugins
      faroUploader({
        appName: "$your-app-name",
        endpoint: "$your-faro-collector-url",
        apiKey: "$your-api-key",
        appId: "$your-app-id",
        gzipContents: true,
      }),
    ],
  };

Configuration Options

The following options are available for the Faro JavaScript bundler plugins:

• appName: string required: The name of your application, it should match the appName value used in your Faro Web SDK configuration
• endpoint: string required: The URL of your Faro Collector endpoint, found in Frontend Observability under Settings and Source Maps
• apiKey: string required: The API key for your Faro Collector, you can generate a new scope on [grafana.com], refer to the Obtain an API key section
• appId: string required: The ID of your application, it should match the appId value used in your Faro Web SDK configuration
• stackId: string required: The ID of the stack, found in Frontend Observability under Settings and Source Maps
• outputFiles: string[] optional: An array of source map files to upload, by default Faro uploads all source maps
• bundleId: string optional: The ID of the bundle/build, by default auto-generated, or specify an ID to filter by bundle ID in Frontend Observability
• keepSourcemaps: boolean optional: Whether to keep the source maps in your generated bundle after uploading, default false
• gzipContents: boolean optional: Whether to archive and compress the source maps before uploading, default true
• verbose: boolean optional: Whether to log verbose output during the upload process, default false

After initial configuration, the Faro JavaScript bundler plugins automatically uploads your source maps to Grafana Cloud when you build your application. You can verify that the source maps upload successfully by in the Settings > Source Maps tab in the Frontend Observability plugin. From there you are able to see the source maps that you have uploaded.

After you have completed all the required steps, you have finished - the Faro Collector begins processing your source maps and associating them with your telemetry data. The portions of your stack traces with source maps uploaded to the Faro Collector are automatically de-obfuscated and displayed in the Frontend Observability plugin when viewing your error data.