Add Sentry as a GitLab managed app
Problem to solve
Currently we integrate with Sentry, but we do not offer an easy way to deploy an instance to a user's attached Kubernetes cluster. Making Sentry a managed app for makes it simpler for users to get up and running on the platform offering faster time to value leading to wider adoption. Management of this service will become easier when colocated with the applications our users are responsible for.
Furthermore, this will allow our internal teams to easily dogfood this integrated workflow in our auto-devops projects.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
This work supports the Error Tracking Vision.
Add Sentry to our Cluster Apps list, and automatically enable the integration on both sides. There exists a helm chart for Sentry.
HOWEVER, the community helm chart has a warning (as mentioned in the README) that we will potentially have to fix as part of implementation. Here is the warning:
Warning: This Chart does not support helm upgrade an upgrade will currently reset your installation
We are spiking on implementation prior to the start of
12.6 and that research will inform commitment.
We will be implementing this using the CI-based GitLab-Managed-Apps V2.
Tasks to complete:
- Add CI configuration for Sentry cluster application install
- Write documentation to help users install
- Frontend work to advertise the fact we support Sentry managed app
After discussing with the Configure:Orchestration team, we decided that the integration won't be discoverable in the UI for the first iteration, as we don't want to introduce a new UI that mimics the existing UI for installing applications but doesn't follow the same pattern as it could be confusing for users. We may need to make additional updates to the UI in subsequent iterations, depending on how work progresses as part of &2103
What does success look like, and how can we measure that?
One click to enable Error Tracking in GitLab.