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
@@ -21,6 +21,7 @@ For example, the config object may look similar to the following:
21
21
| allowCookies | Boolean |`false`| Enable the web client to set and read two cookies: a session cookie named `cwr_s` and a user cookie named `cwr_u`.<br/><br/>`cwr_s` stores session data including an anonymous session ID (uuid v4) created by the web client. This allows CloudWatch RUM to compute sessionized metrics like errors per session.<br/><br/>`cwr_u` stores an anonymous user ID (uuid v4) created by the web client. This allows CloudWatch RUM to count return visitors.<br/><br/>`true`: the web client will use cookies<br/>`false`: the web client will not use cookies. |
22
22
| releaseId | String |`undefined`| The releaseId will be used to retrieve source map(s), if any, when RUM service unminifies JavaScript error stack traces. It should be unique to each application release and match regex ^[a-zA-Z0-9_\-:/\.]{1,200}$, including size limit of 200. |
23
23
| cookieAttributes |[CookieAttributes](#cookieattributes)|`{ domain: window.location.hostname, path: '/', sameSite: 'Strict', secure: true, unique: false } `| Cookie attributes are applied to all cookies stored by the web client, including `cwr_s` and `cwr_u`. |
24
+
| debug | Boolean |`false`| When this field is `true`, the web client will output detailed debug logs to the browser console. These logs include session lifecycle events, plugin operations, dispatch activities, and error details. Debug logs are prefixed with `[aws-rum-web:ClassName.methodName]` for easy identification.<br/><br/>**Note:** Debug mode should only be enabled during development or troubleshooting as it may impact performance and expose internal operations. |
24
25
| sessionAttributes |[MetadataAttributes](#metadataattributes)|`{}`| Session attributes will be added the metadata of all events in the session. |
25
26
| 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
27
| enableRumClient | Boolean |`true`| When this field is `true`, the web client will record and dispatch RUM events. |
@@ -43,7 +44,7 @@ For example, the config object may look similar to the following:
43
44
| telemetries |[Telemetry Config Array](#telemetry-config-array)|`[]`| See [Telemetry Config Array](#telemetry-config-array)|
44
45
| batchLimit | Number |`100`| The maximum number of events that will be sent in one batch of RUM events. |
45
46
| dispatchInterval | Number |`5000`| The frequency (in milliseconds) in which the webclient will dispatch a batch of RUM events. RUM events are first cached and then automatically dispatched at this set interval. |
46
-
| eventCacheSize | Number |`200`| The maximum number of events the cache can contain before dropping events. |
47
+
| eventCacheSize | Number |`500`| The maximum number of events the cache can contain before dropping events. |
47
48
| sessionLengthSeconds | Number |`1800`| The duration of a session (in seconds). |
48
49
| headers | Object |`{}`| The **headers** configuration is optional and allows you to include custom headers in an HTTP request. For example, you can use it to pass `Authorization` and `x-api-key` headers.<br/><br/>For more details, see: [MDN - Request Headers](https://developer.mozilla.org/en-US/docs/Glossary/Request_header). |
0 commit comments