faro-web-sdk
faro-web-sdk copied to clipboard
The Grafana Faro Web SDK, part of the Grafana Faro project, is a highly configurable web SDK for real user monitoring (RUM) that instruments browser frontend applications to capture observability sign...
Update the README and cloud docs to reflect the whole picture how to to use Faro with Grafana Cloud and Grafan Agent. For example: * Have a good textual description...
## Description Based on issue #131 I have managed to get partially propagate cors trace headers. I expected to also get the `tracestate` header propagated, but I am only getting...
## Description We propose enhancing the Grafana Faro Receiver component by adding basic authentication or HTTP header options specifically for the sourcemaps block. Currently, the sourcemaps should be publicly accessible....
## Description Faro uses an old Yarn version which is in maintenance mode and will be deprecated eventually. ## Proposed solution Upgrade yarn to most recent version ## Context
## Why Instead of loading individual web pages per user navigation, Single Page Applications (SPAs) use _soft-navigations_ when a user navigates the app. Here, the content of a page is...
## Description Capturing metrics with a cloud based instance floods console with errors because of the users adblockers ## Steps to reproduce 1. Add Faro to the project 2. Send...
There is an exception throwing when installing this package in the ReactJS typescript application. Instalation is success but when using this package in code, (when importing from package this expectation...
## Description I integrated faro-react-sdk into an electron app and it properly annotates the page id when using the `ReactIntegration` for react router v6 ```react ( )} > {getRoutes()} {getBackgroundComponents()}...
## Description Context data attached to a error via the context object gets lost in the backend when using Grafana Agent. ```ts aro.api.pushError(error, { type: 'network', context: { message: 'React...
## Description Current version of React Router logs only destination of route. It would be useful if previous route also was logged. Example of an event: ``` { "events": [...