As per browser logs to locate errors in the source

[Fine0830]

Background

The information obtained by looking at the JS error details is not enough to diagnose the problem, as the online code is generally compiled, compressed, confused and so on, so the JS code we see is not readable. Although we know that the error occurred in line 1, column 9999, it does not mean that it is the actual location of the source code. At this point, we need to use source map for source mapping.

Functions

1. Upload and manage Source Map files on booster ui.
2. Source mapping
3. Show the Source mapping results on booster ui.

[yangmiao7]

@Fine0830
Hi there,

I have been following the Skywalking project for over a year and I'm interested in using the Browser Logs feature for frontend monitoring and error tracking. I'm wondering if there are any plans to implement the Source Mapping feature in the near future? This feature is critical for pinpointing the exact location of errors in the source code, which would greatly improve the debugging process.

Could you kindly provide an update on the status of this feature and when it might be available? I appreciate all the hard work that goes into maintaining this project and look forward to hearing back from you.

Thank you.

[wu-sheng]

I think we are not working on this yet.

[yangmiao7]

@wu-sheng
Thank you for your response.
Do you have any plans to implement this feature in the future or is it currently not on the roadmap? Having the Source Mapping feature would be a valuable addition to the Browser Logs feature and would greatly benefit the community who are using Skywalking for frontend monitoring and error tracking.

[Fine0830]

Probably I can implement it in the 9.6.0.

[wu-sheng]

@wu-sheng

Thank you for your response.

Do you have any plans to implement this feature in the future or is it currently not on the roadmap? Having the Source Mapping feature would be a valuable addition to the Browser Logs feature and would greatly benefit the community who are using Skywalking for frontend monitoring and error tracking.

We know it is valuable, that is why we are tracking this.
But we have our own priority, as no volunteer is willing to do this, it seems not a high priority work.
That is how a community works.

[dohard-ma]

Looking forward to the launch of this function, I can participate in the development of this function

[wu-sheng]

If you want to do this, I could assign this to you. Right now, no one is working on this AFAIk.

[dohard-ma]

OK, I'll make an implementation plan, and then I'll ask you for confirmation