Comparing
ta/integrate-sentry-to-logger
(7bf221a
) withta/create-logger-abstraction
(6832819
)+1%
- Untouched
- 3
Benchmarks
Passed
Commits
Click on a commit to change the comparison rangeBase
ta/create-logger-abstraction
6832819
-0.17%
Integrate Sentry to the server portal
Still needs some tuning. I'm not sure
if the results we are getting are useful
at the moment.
94c7f8f
10 months ago
by Tzal3x+0.33%
Refactor common lib logs to process them as Sentry tags
70495e3
10 months ago
by Tzal3x+0.22%
Stringify fetchedResourceResult to be displayed to Sentry tags
17e23f5
10 months ago
by Tzal3x-0.37%
Add missing log errors
3ad737d
10 months ago
by Tzal3x+0.54%
Add more log errors
80090a6
10 months ago
by Tzal3x-0.39%
refactor(common): rephrase and enrich logs (#305)
251b82d
10 months ago
by Tzal3x-0.36%
Create SENTRY_DSN env variable
This will be saved as a vercel
environment variable.
DSNs are safe to keep public because
they only allow submission of new
events and related event data;
they do not allow read access to any
information.
While there is a risk of abusing a DSN,
where any user can send events to your
organization with any information they want,
this is a rare occurrence.
So just to be safe 100%, we will use a vercel
environment variable for it.
1cc4e59
10 months ago
by Tzal3x+0.74%
feat(common): add a new -debug- logging level (#307)
- Create a new debug level, used as the highest level of logging.
- Add more descriptive comments to the logger class.
- Update the logging level of some of the logs used in the server
portal.
7bf221a
10 months ago
by Tzal3x