Flow doc site: error tracking integration
Open
Nobody has claimed this yet.
Developer Tool Team
Feature
Feedback
- Dominant language
- Go
- Stars
- 361
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
Issue To Be Solved
We lack of the capability of error reporting, leaving us in a state where we rely on users to report such errors. To be able to proactively identify & address problems, it's recommended to leverage a modern error tracking system
(Optional): Suggest A Solution
Sentry could be a good fit for this purpose; open to using any other tools that are easy to integrate & can achieve the goal
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 locating the Flow doc site's deployment and current error-reporting boundary. Evaluate Sentry or another easy-to-integrate tool, then define success as errors being captured so maintainers can identify and address problems proactively.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100