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
Currently, the ignore function of the 'errors' telemetry takes the raw error event as an argument to let the developer choose whether to ignore it or not. However, this is not consistent with the way the error is reported back to the AWS RUM console as several transformations are applied to the error object to produce the event sent to RUM.
It makes adjusting the ignore function quite tricky only using the RUM console.
Wouldn't it easier to provide an alternative function that can filter the event based on the transformed data?
It would even allow the developer to filter based on the metadata aws rum adds to the event (like the web browser, the user id, the session, etc.)
Thanks.
The text was updated successfully, but these errors were encountered:
Please provide your feature request
Hi,
Currently, the
ignore
function of the'errors'
telemetry takes the raw error event as an argument to let the developer choose whether to ignore it or not. However, this is not consistent with the way the error is reported back to the AWS RUM console as several transformations are applied to the error object to produce the event sent to RUM.It makes adjusting the ignore function quite tricky only using the RUM console.
Wouldn't it easier to provide an alternative function that can filter the event based on the transformed data?
It would even allow the developer to filter based on the metadata aws rum adds to the event (like the web browser, the user id, the session, etc.)
Thanks.
The text was updated successfully, but these errors were encountered: