---
# generated by https://github.com/hashicorp/terraform-plugin-docs
page_title: "awscc_rum_app_monitor Data Source - terraform-provider-awscc"
subcategory: ""
description: |-
  Data Source schema for AWS::RUM::AppMonitor
---

# awscc_rum_app_monitor (Data Source)

Data Source schema for AWS::RUM::AppMonitor



<!-- schema generated by tfplugindocs -->
## Schema

### Required

- `id` (String) Uniquely identifies the resource.

### Read-Only

- `app_monitor_configuration` (Attributes) AppMonitor configuration (see [below for nested schema](#nestedatt--app_monitor_configuration))
- `cw_log_enabled` (Boolean) 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 CWLlong in your account. This enables you to keep the telemetry data for more than 30 days, but it does incur CWLlong charges. If you omit this parameter, the default is false
- `domain` (String) The top-level internet domain name for which your application has administrative authority.
- `name` (String) A name for the app monitor
- `tags` (Attributes Set) 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 AWS and are interpreted strictly as strings of characters.You can associate as many as 50 tags with an app monitor. (see [below for nested schema](#nestedatt--tags))

<a id="nestedatt--app_monitor_configuration"></a>
### Nested Schema for `app_monitor_configuration`

Read-Only:

- `allow_cookies` (Boolean) 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.
- `enable_x_ray` (Boolean) If you set this to true, RUM enables xray tracing for the user sessions that RUM samples. RUM adds an xray trace header to allowed HTTP requests. It also records an xray segment for allowed HTTP requests. You can see traces and segments from these user sessions in the xray console and the CW ServiceLens console.
- `excluded_pages` (List of String) 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.
- `favorite_pages` (List of String) A list of pages in the RUM console that are to be displayed with a favorite icon.
- `guest_role_arn` (String) The ARN of the guest IAM role that is attached to the identity pool that is used to authorize the sending of data to RUM.
- `identity_pool_id` (String) The ID of the identity pool that is used to authorize the sending of data to RUM.
- `included_pages` (List of String) 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.
- `session_sample_rate` (Number) Specifies the percentage of user sessions to use for RUM data collection. Choosing a higher percentage gives you more data but also incurs more costs. The number you specify is the percentage of user sessions that will be used. If you omit this parameter, the default of 10 is used.
- `telemetries` (List of String) An array that lists the types of telemetry data that this app monitor is to collect.


<a id="nestedatt--tags"></a>
### Nested Schema for `tags`

Read-Only:

- `key` (String) The key name of the tag. You can specify a value that is 1 to 128 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.
- `value` (String) The value for the tag. You can specify a value that is 0 to 256 Unicode characters in length and cannot be prefixed with aws:. You can use any of the following characters: the set of Unicode letters, digits, whitespace, _, ., /, =, +, and -.