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...
## Description Enabling the Tracing Instrumentation in a Next13 project (App Router) with Faro breaks link that use prefetching (which is set to true for all links by default). ##...
## Description When working with Single Page Apps (SPA), an application is decomposed into views / routes. The current faro api doesn't allow submitting attributes for views though. ## Proposed...
adding a CLI package for tools like source map uploads and potentially more in the future
## Description Faro stores some session information in the browsers web-storage. If multiple Faro instances are used within a micro frontend app they all use the same object from the...
## Description Given you have: - Webserver - Grafana-Agent - Faro SDK w/ tracing If you hit /collect from your app, using a relative path, then faro will create a...
## Description I get the following errors when I add TracingInstrumentation to my NextJS application. ``` Unhandled Promise rejection: Cannot find module for page: /en ; Zone: ; Task: Promise.then...
## Description :wave: web sdk allows posting events with attributes of type `number`, but Grafana cloud endpoint fails to parse them with error: ``` json: cannot unmarshal number into Go...
## Description Hello community, when running the docker compose command, the only demo container failed to start. It is curious because others containers also contains volume mount and does not...
## Description  ## Steps to reproduce docker compose --profile demo up -d ## Expected behavior ## Actual behavior I'm using the docker-compose.yaml from the repository, but the metrics...
## Description Using different OTel versions can cause problems if Faro would not used the version as specified. ## Proposed solution Declare respective packages as peer-dependencies