-
Notifications
You must be signed in to change notification settings - Fork 8
Jaeger Implementation for Frontend #80
Comments
After the first implementation, some fixes are done now to PR #81:
Remaining problems:
In the next commit these features are planned to be included:
@arkocal let me know if you need anything else. |
For checking whether the platform is running on docker or kubernetes, you can check the env variable |
With the new commits to PR #81:
In the next commit, I will be polishing the span handling (more and nicer tags (for example tagging requests that produced an error)). More or less, the jaeger implementation for frontend is done. @arkocal let me know if you need something else. |
With the new commits to PR #81:
With this, this pr should be stable and we can merge it. |
Apparently for jaeger to work properly, we need to solve the context provider bug mentioned at #103. |
To implement Jaeger, we need to listen:
This way we can benchmark our code better and see exactly how much time every route consumes.
The text was updated successfully, but these errors were encountered: