search

gitcoinambassadors / ideas

Long-form pitching of Ambassador Project Ideas
7 stars 2 forks source link

Proposal/Idea: Support core-team analyzing Sentry #8

Open kuhnchris opened 5 years ago

kuhnchris commented 5 years ago

User Story

As development-centered supporter of GitCoin it may make sense to take a look at the productive sentry and help/monitor the errors popping up from time to time.

Why Is this Needed

To have a clean platform it makes sense that we take a look at the occouring errors before user actually take note of them. That may happen by taking a look at what happens behind the scenes.

Description

Type: Idea / Request

Current Behavior

We are looking at a black box and/or asking core team members silly/stupid questions regarding possible (wrong) solutions where the solution may be due to an error on the back/frontend in plain sight, until a core-team member (or @mbeacom ) takes a look at it.

Expected Behavior

During errors on Sentry the ambassador team can support the core team with already pre-analyzed issues regarding the occouring problems.

Additional Information

THIS MAY NOT WORK AT ALL I am not sure if we hide stuff like access codes (from github/user auth) or passwords, so it may very well be (and reasonable) that we will never get access to that, aside from core team. This is just an idea to reduce the burden on the "monitoring" and "backlogging" side of things for the core team, so they can focus on SHIP new stuff.

rmshea commented 5 years ago

This is certainly something I'd like to look into -- one of our biggest bottlenecks arises from this.

What would a sentry look like in this case? Slackbot-esque?

kuhnchris commented 5 years ago

I could not tell you, as I never used Sentry. We only get a couple of links where the core-team refers to sentry issues, but we cannot see them at all. Hence we'd need an example from @owocki for example.