2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
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