Monitoring settings

Overview

This topic describes the project-level settings available for sessions, errors, logs, and traces.

You can find LaunchDarkly’s observability features in the LaunchDarkly UI in the left navigation, under the “Monitor” heading.

To view or update project-level settings for these features:

1. Click the project dropdown to open the project menu.
2. Select Project settings.
3. Click Monitoring. The Monitoring settings page appears.

The following sections describe the available settings.

Session settings

You can configure the following settings for sessions in your project:

• Excluded users. This setting excludes sessions from particular end users, based on their context key or email address.
• Rage clicks. These settings adjust the sensitivity for detecting “rage clicks,” or occasions when end users repeatedly click an element in your application, indicating frustration. You can set the Elapsed time, Radius, and Minimum clicks. These settings control whether a search for session replays that uses the has_rage_clicks attribute will return a given session.

Click Save to save your settings.

Error settings

You can configure the following settings for errors in your project:

• Sourcemaps. If you have uploaded sourcemaps, you can view them here.
• Auto-resolve stale errors. When enabled, this setting automatically sets the status of an error to “Resolved” after the time period you select.

Click Save to save your settings.

Filters

You can filter out sessions, errors, logs, or traces that you do not want to view in LaunchDarkly before they are ingested. This is useful if you know the data is not relevant to your application, or is not actionable. Filtered sessions, errors, logs, and traces do not count against your observability quotas.

To set up ingestion filtering:

1. Navigate to the Monitoring settings page.
2. From the Filters section, click Edit next to the type of filter you want to set.
   • Alternatively, click Session filters or Error filters from the Sessions or Errors sections, respectively.
3. (Optional) Set the Sampling %. For each session, error, log, or trace record that LaunchDarkly receives, it makes a randomized decision that results in storing only the indicated percentage of all records.
4. (Optional) Set the Max ingest per minute. This setting rate limits the maximum number of data points ingested in a one-minute window. For example, you may configure a rate limit of 100 per minute. This lets you limit the number of data points recorded in case of a significant spike in use of your application.
5. (Optional) Set a rule to exclude certain sessions, errors, logs, or traces based on available attributes.
   • Click the Search… placeholder and select an attribute from the dropdown. For example, you can exclude sessions based on active_length.
     • For details on the available attributes, read Search attributes for session replay, Search attributes for errors, Search attributes for logs, and Search attributes for traces.
   • Select an operator from the dropdown. For example, you can filter by greater than, >.
   • Enter a value for your expression. For example, you can enter 8s for eight seconds.
   • Here is an example of a session filter rule:

     

6. Click Save changes.