2 Answers
- Newest
- Most votes
- Most comments
0
Hello, and thanks for reaching out!
When configuring the telemetries parameters in the config and specifying non-default options, you'll want to be sure to specify each telemetry as its own array, as seen in the examples here.
Try specifying the telemetries as the following and let me know if you see any changes in behavior:
telemetries: ["performance","errors",["http",{recordAllRequests: true}]],
0
I have forked the RUM client. Quick fix for our specific use case, but it tracks ALL API calls (including after initial page load and ignoring max events configuration) as performance metrics.
You will have to force the OTHER type in all recorded types rather than sampled
telemetries: [
[ "performance", {recordAllTypes: ['document', 'script', 'other']} ],
"errors",
"http"
],
https://github.com/samholton/aws-rum-web/releases/tag/v1.5.1-api-patch
answered 3 years ago
Relevant content
- asked a year ago
- asked 4 months ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago
I am experiencing the same thing with a React APP. Not seeing any of the
com.amazon.rum.http_event
on the console for API calls being made. I have