Manage RUM MetricSets

Create, edit, pause, and delete RUM MetricSets.

You can use the APM & RUM MetricSets page to view and manage your RUM Monitoring MetricSets (MMS) and Troubleshooting MetricSets (TMS).

Prerequisites

You need the admin role in Splunk Observability Cloud to create, edit, pause, and delete RUM MetricSets.

Access the APM & RUM MetricSets page

You can use either of the following options to access the APM & RUM MetricSets page:

  • In the Splunk Observability Cloud main menu, select Settings > APM & RUM MetricSets > RUM.

  • In the Splunk Observability Cloud main menu, select Digital Experience. In the Real user monitoring section, select Overview. Select the RUM Configuration drop-down menu in the upper-right corner, then RUM MetricSet.

Manage default and custom MMS

In the APM & RUM MetricSets table, select the actions (…) menu in the row for the MMS to:

  • Edit or pause default MMS.

  • Edit, pause, or delete custom MMS.

For instructions on how to create a custom MMS, see Create a Monitoring MetricSet with a custom dimension.

Manage custom TMS

In the APM & RUM MetricSets table, select the actions (…) menu in the row for the TMS to pause, edit, or delete custom TMS. Default TMS are always enabled and can't be changed.

For instructions on how to create a custom TMS, see Index span tags to create a Troubleshooting MetricSet.

Understand cardinality for MMS and TMS

In the APM & RUM MetricSets table, the Unique URL column displays the number of unique URLs that are active for a MetricSet. The App coverage column displays the number of applications that the MetricSet applies to, and can either show a value of All applications or list the number of applications covered out of all of your applications. You can use these columns to understand the cardinality of a MetricSet.

Higher numbers may indicate that the MetricSet has high cardinality, meaning that it applies to many applications and has many unique values. High-cardinality MetricSets are useful because they provide granular insights into your applications.

Lower numbers may indicate that the MetricSet has low cardinality, meaning that it could be updated to provide more visibility into your application data.