marcanpilami opened a new issue, #11662:
URL: https://github.com/apache/skywalking/issues/11662

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache SkyWalking Component
   
   NodeJS Client Side Agent (apache/skywalking-client-js)
   
   ### What happened
   
   I set up the JS library (inside a React app but this may not be relevant). 
Data is pushed correctly to the OAP server by the browser (HTTP 200, and data 
is present inside the OpenSearch database).
   
   However, the data cannot be seen inside the browser layer dashboards of the 
UI. Trace data can however be seen inside the traces of other components (in my 
case a java agent for the application backend), so data is here, and the trace 
id is well understood.
   
   
   
   ### What you expected to happen
   
   I would expect the browser layer dashboard to show my traces and errors.
   
   ### How to reproduce
   
   It should work with any default configuration, here given as a React hook 
run on startup in the root component:
   ```js
   useEffect(() => {
           if (window.APP_APIM_ENABLED) {
               ClientMonitor.register({
                   collector: window.APP_APIM_URL,
                   service: window.APP_APIM_PROJECT_NAME,
                   pagePath: '/app',
                   serviceVersion: 'v1.0.0',
                   useFmp: true,
                   enableSPA: true,
                   noTraceOrigins: [],
                   customTags: [],
                   traceTimeInterval: 1000,
               });
           }
       },
           [] // on startup only.
       );
   ```
   
   ### Anything else
   
   It seems the dashboards look for data in the BROWSER layer, but the JS 
library reports its spans as HTTP layer, hence the lack of data. Is this 
mismatch voluntary, or does it mean the BROWSER layer is for something else 
entirely? I have not found a way to overload the JS layer constant to test this 
hypothesis.
   
   If this is simply a matter of changing the constant or making it 
configurable, I'm open to submitting a PR.
   
   And.. thanks a lot for all your hard work on Skywalking!
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to