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.
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.