[Feature Request] Create OpenTelemetry instrument on callbacks of Dash
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Is your feature request related to a problem? Please describe.
In the context of an industrialization of the use of Dash entreperise and Dash for all our research dash application we are facing the problme of offering usable metric to our dev teams to maintain these mini websites. The commonly accepted standard in the telemetry community seems to be openTelemetry, as it's well digested by Azure app insight, Grafana, Jaeger etc....
At this stage there is no out of the box solution to easily implement instruments on top of the Dash application (or I didn't find it) and I'm starting to reinvent the wheel.
Describe the solution you'd like
- A first step would be to add a way to instrument the callback methods so it can report interaction on the dashboards: error, buttons clicked, data used.
- A second step would be to do the same for pages load when using multipage dash app
- Finally the most complicated feature for me is to get a glimpse of when people are entering and exiting an app and who they were (if the app is authenticated). obviously the objective is to encapsulate all the previous mentioned spans into a more global one to have an overview of the "user journey".
Describe alternatives you've considered
I am currently reinventing the wheel internally but I think this functionnality will benefit every users of Dash. so I'm making my problem public.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping Dash callback and multipage request flows, then define separate acceptance criteria for callback, page-load, and authenticated user-journey instrumentation before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100