feat(frontend): Add better frontend tracing#11244
feat(frontend): Add better frontend tracing#11244SchrodingersGat merged 14 commits intoinventree:masterfrom
Conversation
✅ Deploy Preview for inventree-web-pui-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (42.10%) is below the target coverage (95.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## master #11244 +/- ##
==========================================
- Coverage 88.08% 87.88% -0.21%
==========================================
Files 1292 1292
Lines 58481 58990 +509
Branches 1943 1943
==========================================
+ Hits 51512 51841 +329
- Misses 6485 6665 +180
Partials 484 484
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
Should we be concerned about the extra (albeit small) overhead associated with the extra API call to end the trace? Have you profiled this in action? |
|
I have profiled it on my test setup and the duration for the whole interaction is at about 50-65 ms as it does not really do much intensive action |
|
@matmair happy with this if you can fix conflicts, so we can get to the 1.2.0 |
|
I have adressed the conflict |

This PR gives us a generic way to associated API calls with a single event in the frontend. This is helpful to more easily find bottlenecks like serial API calls that do not depend on each other, API calls that are always grouped and access the same data and much more.
Changeset is kept minimal to get some practice with the process around the gathered analytics before we maybe extend OTEL to the frontend - which is much more involved data and security wise.