You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configuration.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ For example, the config object may look similar to the following:
25
25
| disableAutoPageView | Boolean |`false`| When this field is `false`, the web client will automatically record page views.<br/><br/>By default, the web client records page views when (1) the page first loads and (2) the browser's [history API](https://developer.mozilla.org/en-US/docs/Web/API/History_API) is called. The page ID is `window.location.pathname`.<br/><br/>In some cases, the web client's instrumentation will not record the desired page ID. In this case, the web client's page view automation must be disabled using the `disableAutoPageView` configuration, and the application must be instrumented to record page views using the `recordPageView` command. |
26
26
| enableRumClient | Boolean |`true`| When this field is `true`, the web client will record and dispatch RUM events. |
27
27
| enableXRay | Boolean |`false`| When this field is `true`**and** the `http` telemetry is used, the web client will record X-Ray traces for HTTP requests.<br/><br/>See the [HTTP telemetry configuration](#http) for more information, including how to connect client-side and server-side traces. |
28
+
| enableW3CTraceId | Boolean |`false`| When this field is `true`**and** the `enableXRay` field is `true`**and** the `http` telemetry is used, the web client will record X-Ray traces for HTTP requests in the W3C trace ID format.<br/><br/>Note that existing X-Ray headers will be ignored if this is enabled, and existing W3C headers will be ignored if this is disabled.<br/><br/>See the [W3C Trace Format Specification](https://www.w3.org/TR/trace-context/) for more information. |
28
29
| endpoint | String |`'https://dataplane.rum.[region].amazonaws.com'`<br/><br/>`'https://[restapi_id].execute-api.[region].amazonaws.com/[stage_name]/'`| The URL of the CloudWatch RUM API where data will be sent.<br/><br/>You may include a path prefix like `/stage_name/` in the endpoint URL if there is a proxy between your web application and CloudWatch RUM. |
29
30
| eventPluginsToLoad |[Plugin](examples.md#record-custom-events-using-a-plugin)[]|`[]`| The set of custom plugins to load. See [usage examples](examples.md#record-custom-events-using-a-plugin). |
30
31
| guestRoleArn | String |`undefined`| The ARN of the AWS IAM role that will be assumed during anonymous authorization.<br/><br/>When `guestRoleArn` and `identityPoolId` are both set, the web client will use Cognito's [basic (classic) authflow](https://docs.aws.amazon.com/cognito/latest/developerguide/authentication-flow.html).<br/><br/>When only `identityPoolId` is set, the web client will use Cognito's [enhanced (simplified) authflow](https://docs.aws.amazon.com/cognito/latest/developerguide/authentication-flow.html) (recommended). |
@@ -134,7 +135,7 @@ telemetries: [
134
135
| urlsToExclude | RegExp[]|`[]`| A list of HTTP request (`XMLHttpRequest` or `fetch`) URLs. These requests will not be recorded. |
135
136
| stackTraceLength | Number |`1000 `| The number of characters to record from a JavaScript error's stack trace (if available). |
136
137
| recordAllRequests | boolean |`false`| By default, only HTTP failed requests (i.e., those with network errors or status codes which are not 2xx) are recorded. When this field is `true`, the http telemetry will record all requests, including those with successful 2xx status codes. <br/><br/>This field does **does not apply** to X-Ray traces, where all requests are recorded. |
137
-
| addXRayTraceIdHeader | boolean or RegExp[]|`false`| By default, the `X-Amzn-Trace-Id` header will not be added to the HTTP request. This means that the client-side trace and server-side trace will **not be linked** in X-Ray or the ServiceLens graph.<br/><br/> When this field is `true`, the `X-Amzn-Trace-Id` header will be added to HTTP requests (`XMLHttpRequest` or `fetch`).<br/><br/> When this field is an array of regular expressions (RegExp[]), the `X-Amzn-Trace-Id` header will be added only to HTTP requests that contain an URL matching one or more of the regular expressions.<br/><br/>**Adding the `X-Amzn-Trace-Id` header can cause CORS failures. Test your application before enabling this feature in a production environment.**|
138
+
| addXRayTraceIdHeader | boolean or RegExp[]|`false`| By default, the `X-Amzn-Trace-Id` header will not be added to the HTTP request. This means that the client-side trace and server-side trace will **not be linked** in X-Ray or the ServiceLens graph.<br/><br/> When this field is `true`, the `X-Amzn-Trace-Id` header will be added to HTTP requests (`XMLHttpRequest` or `fetch`).<br/><br/> When this field is an array of regular expressions (RegExp[]), the `X-Amzn-Trace-Id` header will be added only to HTTP requests that contain an URL matching one or more of the regular expressions. If the `enableW3CTraceId` field is set to true, then a `traceparent` header will be added in the W3C trace format (see [here](https://www.w3.org/TR/trace-context/#traceparent-header) for more information) instead of the `X-Amzn-Trace-Id` header. <br/><br/>**Adding the `X-Amzn-Trace-Id` header can cause CORS failures. Test your application before enabling this feature in a production environment.**|
0 commit comments