Page MenuHomeSoftware Heritage

Setup a sentry service
Closed, MigratedEdits Locked

Event Timeline

vlorentz triaged this task as Normal priority.Dec 5 2018, 5:31 PM
vlorentz raised the priority of this task from Normal to High.Dec 3 2019, 3:17 PM
olasd changed the task status from Open to Work in Progress.Dec 6 2019, 11:06 PM
olasd added a subscriber: olasd.

I think I've mostly coerced sentry, at url https://sentry.softwareheritage.org/, into working. I used the opportunity to start refactoring the way apache is handled in our puppet environment, as well as slowly migrating some vhosts to Let's Encrypt.

All in all I've spent way too much time on some stupid docker-compose environment variables stuff, and the (afaik, advertised) way I set the kafka broker URIs was never taken into account. *sigh*.

User accounts are self-service for now. We should be able to integrate with keycloak using the OIDC plugin by Siemens: https://github.com/siemens/sentry-auth-oidc. (I'll avoid mentioning why this hasn't been integrated by upstream, the mind boggles...)

The next steps would be:

  • looking at the phabricator integration (which at this point only allows to create tasks (manually) from sentry)
  • figure out how to do repository integration
olasd claimed this task.

Sentry is now available at https://sentry.softwareheritage.org/.

(Basic) integration has landed for most services.

For now, you need to create an account by going to the "request to join" tab and following the instructions.

I'll create followup tasks for the rest of the things we want to do.

gitlab-migration changed the status of subtask T1360: Install a sentry server from Resolved to Migrated.