Consider moving Sentry out of lightning
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
As a new developer, if I've got no plans to do error monitoring via Sentry (either self-hosted or the Sentry SaaS) I shouldn't have to see it in this repo. (And it shouldn't start any processes.)
Adding sentry should be the responsibility of the organization that's deploying/managing Lightning.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by locating the Sentry integration and any process startup it triggers; done means Lightning no longer includes or starts Sentry by default, while deployment organizations can add and manage it themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100