This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter.

This parameter specifies the ARN of the Evidently experiment that is to receive the metrics. You must have already defined this experiment as a valid destination. For more information, see PutRumMetricsDestination.

The name of the CloudWatch RUM app monitor that is to send the metrics.

The destination to send the metrics to. Valid values are CloudWatch and Evidently. If you specify Evidently, you must also specify the ARN of the CloudWatchEvidently experiment that will receive the metrics and an IAM role that has permission to write to the experiment.

An array of structures which define the metrics that you want to send.

An array of structures that define the extended metrics.

The response's http status code.

An array of error objects, if the operation caused any errors.

This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter.

This parameter specifies the ARN of the Evidently experiment that was receiving the metrics that are being deleted.

The name of the CloudWatch RUM app monitor that is sending these metrics.

Defines the destination where you want to stop sending the specified metrics. Valid values are CloudWatch and Evidently. If you specify Evidently, you must also specify the ARN of the CloudWatchEvidently experiment that is to be the destination and an IAM role that has permission to write to the experiment.

An array of structures which define the metrics that you want to stop sending.

The IDs of the metric definitions that were deleted.

The response's http status code.

An array of error objects, if the operation caused any errors.

This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter.

This parameter specifies the ARN of the Evidently experiment that corresponds to the destination.

The maximum number of results to return in one operation. The default is 50. The maximum that you can specify is 100.

To retrieve the remaining results, make another call with the returned NextToken value.

Use the token returned by the previous operation to request the next page of results.

The name of the CloudWatch RUM app monitor that is sending the metrics.

The type of destination that you want to view metrics for. Valid values are CloudWatch and Evidently.

An array of structures that display information about the metrics that are sent by the specified app monitor to the specified destination.

A token that you can use in a subsequent operation to retrieve the next set of results.

The response's http status code.

A structure that contains much of the configuration data for the app monitor. If you are using Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own authorization method. For more information, see Authorize your application to send data to Amazon Web Services.

If you omit this argument, the sample rate used for RUM is set to 10% of the user sessions.

Specifies whether this app monitor allows the web client to define and send custom events. If you omit this parameter, custom events are DISABLED.

For more information about custom events, see Send custom events.

Data collected by RUM is kept by RUM for 30 days and then deleted. This parameter specifies whether RUM sends a copy of this telemetry data to Amazon CloudWatch Logs in your account. This enables you to keep the telemetry data for more than 30 days, but it does incur Amazon CloudWatch Logs charges.

If you omit this parameter, the default is false.

Assigns one or more tags (key-value pairs) to the app monitor.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

You can associate as many as 50 tags with an app monitor.

For more information, see Tagging Amazon Web Services resources.

The top-level internet domain name for which your application has administrative authority.

A name for the app monitor.

The unique ID of the new app monitor.

The response's http status code.

The name of the app monitor to delete.

The response's http status code.

This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter. This parameter specifies the ARN of the Evidently experiment that corresponds to the destination to delete.

The name of the app monitor that is sending metrics to the destination that you want to delete.

The type of destination to delete. Valid values are CloudWatch and Evidently.

The response's http status code.

The app monitor to retrieve information for.

A structure containing all the configuration information for the app monitor.

The response's http status code.

An array of structures that you can use to filter the results to those that match one or more sets of key-value pairs that you specify.

The maximum number of results to return in one operation.

Use the token returned by the previous operation to request the next page of results.

The name of the app monitor that collected the data that you want to retrieve.

A structure that defines the time range that you want to retrieve results from.

The events that RUM collected that match your request.

A token that you can use in a subsequent operation to retrieve the next set of results.

The response's http status code.

The maximum number of results to return in one operation. The default is 50. The maximum that you can specify is 100.

Use the token returned by the previous operation to request the next page of results.

An array of structures that contain information about the returned app monitors.

A token that you can use in a subsequent operation to retrieve the next set of results.

The response's http status code.

The maximum number of results to return in one operation. The default is 50. The maximum that you can specify is 100.

To retrieve the remaining results, make another call with the returned NextToken value.

Use the token returned by the previous operation to request the next page of results.

The name of the app monitor associated with the destinations that you want to retrieve.

The list of CloudWatch RUM extended metrics destinations associated with the app monitor that you specified.

A token that you can use in a subsequent operation to retrieve the next set of results.

The response's http status code.

The ARN of the resource that you want to see the tags of.

The response's http status code.

The ARN of the resource that you are viewing.

The list of tag keys and values associated with the resource you specified.

A structure that contains information about the app monitor that collected this telemetry information.

A unique identifier for this batch of RUM event data.

The ID of the app monitor that is sending this data.

An array of structures that contain the telemetry event data.

A structure that contains information about the user session that this batch of events was collected from.

The response's http status code.

Use this parameter only if Destination is Evidently. This parameter specifies the ARN of the Evidently experiment that will receive the extended metrics.

This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter.

This parameter specifies the ARN of an IAM role that RUM will assume to write to the Evidently experiment that you are sending metrics to. This role must have permission to write to that experiment.

The name of the CloudWatch RUM app monitor that will send the metrics.

Defines the destination to send the metrics to. Valid values are CloudWatch and Evidently. If you specify Evidently, you must also specify the ARN of the CloudWatchEvidently experiment that is to be the destination and an IAM role that has permission to write to the experiment.

The response's http status code.

The ARN of the CloudWatch RUM resource that you're adding tags to.

The list of key-value pairs to associate with the resource.

The response's http status code.

The ARN of the CloudWatch RUM resource that you're removing tags from.

The list of tag keys to remove from the resource.

The response's http status code.

A structure that contains much of the configuration data for the app monitor. If you are using Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own authorization method. For more information, see Authorize your application to send data to Amazon Web Services.

Specifies whether this app monitor allows the web client to define and send custom events. The default is for custom events to be DISABLED.

For more information about custom events, see Send custom events.

Data collected by RUM is kept by RUM for 30 days and then deleted. This parameter specifies whether RUM sends a copy of this telemetry data to Amazon CloudWatch Logs in your account. This enables you to keep the telemetry data for more than 30 days, but it does incur Amazon CloudWatch Logs charges.

The top-level internet domain name for which your application has administrative authority.

The name of the app monitor to update.

The response's http status code.

This parameter is required if Destination is Evidently. If Destination is CloudWatch, do not use this parameter.

This parameter specifies the ARN of the Evidently experiment that is to receive the metrics. You must have already defined this experiment as a valid destination. For more information, see PutRumMetricsDestination.

The name of the CloudWatch RUM app monitor that sends these metrics.

The destination to send the metrics to. Valid values are CloudWatch and Evidently. If you specify Evidently, you must also specify the ARN of the CloudWatchEvidently experiment that will receive the metrics and an IAM role that has permission to write to the experiment.

A structure that contains the new definition that you want to use for this metric.

The ID of the metric definition to update.

The response's http status code.

A structure that contains much of the configuration data for the app monitor.

The date and time that this app monitor was created.

Specifies whether this app monitor allows the web client to define and send custom events.

For more information about custom events, see Send custom events.

A structure that contains information about whether this app monitor stores a copy of the telemetry data that RUM collects using CloudWatch Logs.

The top-level internet domain name for which your application has administrative authority.

The unique ID of this app monitor.

The date and time of the most recent changes to this app monitor's configuration.

The name of the app monitor.

The current state of the app monitor.

The list of tag keys and values associated with this app monitor.

If you set this to true, the RUM web client sets two cookies, a session cookie and a user cookie. The cookies allow the RUM web client to collect data relating to the number of users an application has and the behavior of the application across a sequence of events. Cookies are stored in the top-level domain of the current page.

If you set this to true, RUM enables X-Ray tracing for the user sessions that RUM samples. RUM adds an X-Ray trace header to allowed HTTP requests. It also records an X-Ray segment for allowed HTTP requests. You can see traces and segments from these user sessions in the X-Ray console and the CloudWatch ServiceLens console. For more information, see What is X-Ray?

A list of URLs in your website or application to exclude from RUM data collection.

You can't include both ExcludedPages and IncludedPages in the same operation.

A list of pages in your application that are to be displayed with a "favorite" icon in the CloudWatch RUM console.

The ARN of the guest IAM role that is attached to the Amazon Cognito identity pool that is used to authorize the sending of data to RUM.

The ID of the Amazon Cognito identity pool that is used to authorize the sending of data to RUM.

If this app monitor is to collect data from only certain pages in your application, this structure lists those pages.

You can't include both ExcludedPages and IncludedPages in the same operation.

Specifies the portion of user sessions to use for RUM data collection. Choosing a higher portion gives you more data but also incurs more costs.

The range for this value is 0 to 1 inclusive. Setting this to 1 means that 100% of user sessions are sampled, and setting it to 0.1 means that 10% of user sessions are sampled.

If you omit this parameter, the default of 0.1 is used, and 10% of sessions will be sampled.

An array that lists the types of telemetry data that this app monitor is to collect.

• errors indicates that RUM collects data about unhandled JavaScript errors raised by your application.
• performance indicates that RUM collects performance data about how your application and its resources are loaded and rendered. This includes Core Web Vitals.
• http indicates that RUM collects data about HTTP errors thrown by your application.

The unique ID of the app monitor.

The name of the app monitor.

The version of the app monitor.

The date and time that the app monitor was created.

The unique ID of this app monitor.

The date and time of the most recent changes to this app monitor's configuration.

The name of this app monitor.

The current state of this app monitor.

The error code.

The error message for this metric definition.

The metric definition that caused this error.

The error code.

The error message for this metric definition.

The ID of the metric definition that caused this error.

Specifies whether this app monitor allows the web client to define and send custom events. The default is for custom events to be DISABLED.

Indicated whether the app monitor stores copies of the data that RUM collects in CloudWatch Logs.

The name of the log group where the copies are stored.

A structure that contains the information about whether the app monitor stores copies of the data that RUM collects in CloudWatch Logs. If it does, this structure also contains the name of the log group.

This field is a map of field paths to dimension names. It defines the dimensions to associate with this metric in CloudWatch The value of this field is used only if the metric destination is CloudWatch. If the metric destination is Evidently, the value of DimensionKeys is ignored.

The pattern that defines the metric. RUM checks events that happen in a user's session against the pattern, and events that match the pattern are sent to the metric destination.

If the metrics destination is CloudWatch and the event also matches a value in DimensionKeys, then the metric is published with the specified dimensions.

Use this field only if you are sending this metric to CloudWatch. It defines the CloudWatch metric unit that this metric is measured in.

The field within the event object that the metric value is sourced from.

The ID of this metric definition.

The name of the metric that is defined in this structure.

Use this field only if you are sending the metric to CloudWatch.

This field is a map of field paths to dimension names. It defines the dimensions to associate with this metric in CloudWatch. Valid values for the entries in this field are the following:

• "metadata.pageId": "PageId"

• "metadata.browserName": "BrowserName"

• "metadata.deviceType": "DeviceType"

• "metadata.osName": "OSName"

• "metadata.countryCode": "CountryCode"

• "event_details.fileType": "FileType"

All dimensions listed in this field must also be included in EventPattern.

The pattern that defines the metric, specified as a JSON object. RUM checks events that happen in a user's session against the pattern, and events that match the pattern are sent to the metric destination.

When you define extended metrics, the metric definition is not valid if EventPattern is omitted.

Example event patterns:

• '{ "event_type": ["com.amazon.rum.js_error_event"], "metadata": { "browserName": [ "Chrome", "Safari" ], } }'

• '{ "event_type": ["com.amazon.rum.performance_navigation_event"], "metadata": { "browserName": [ "Chrome", "Firefox" ] }, "event_details": { "duration": [{ "numeric": [ "<", 2000 ] }] } }'

• '{ "event_type": ["com.amazon.rum.performance_navigation_event"], "metadata": { "browserName": [ "Chrome", "Safari" ], "countryCode": [ "US" ] }, "event_details": { "duration": [{ "numeric": [ ">=", 2000, "<", 8000 ] }] } }'

If the metrics destination' is CloudWatch and the event also matches a value in DimensionKeys, then the metric is published with the specified dimensions.

The CloudWatch metric unit to use for this metric. If you omit this field, the metric is recorded with no unit.

The field within the event object that the metric value is sourced from.

If you omit this field, a hardcoded value of 1 is pushed as the metric value. This is useful if you just want to count the number of events that the filter catches.

If this metric is sent to CloudWatch Evidently, this field will be passed to Evidently raw and Evidently will handle data extraction from the event.

The name for the metric that is defined in this structure. Valid values are the following:

• PerformanceNavigationDuration

• PerformanceResourceDuration

• NavigationSatisfiedTransaction

• NavigationToleratedTransaction

• NavigationFrustratedTransaction

• WebVitalsCumulativeLayoutShift

• WebVitalsFirstInputDelay

• WebVitalsLargestContentfulPaint

• JsErrorCount

• HttpErrorCount

• SessionCount

Specifies whether the destination is CloudWatch or Evidently.

If the destination is Evidently, this specifies the ARN of the Evidently experiment that receives the metrics.

This field appears only when the destination is Evidently. It specifies the ARN of the IAM role that is used to write to the Evidently experiment that receives the metrics.

The name of a key to search for. The filter returns only the events that match the Name and Values that you specify.

Valid values for Name are Browser | Device | Country | Page | OS | EventType | Invert

The values of the Name that are to be be included in the returned results.

Metadata about this event, which contains a JSON serialization of the identity of the user for this session. The user information comes from information such as the HTTP user-agent request header and document interface.

A string containing details about the event.

A unique ID for this event.

The exact time that this event occurred.

The JSON schema that denotes the type of event this is, such as a page load or a new session.

The end of the time range to retrieve performance events from. If you omit this, the time range extends to the time that this operation is performed.

The beginning of the time range to retrieve performance events from.

The session ID that the performance events are from.

The ID of the user for this user session. This ID is generated by RUM and does not include any personally identifiable information about the user.