Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(logging): update to latest sentry sdk and use LoggerService #384

Merged
merged 6 commits into from
Dec 5, 2019

Conversation

sleidig
Copy link
Member

@sleidig sleidig commented Dec 3, 2019

improved (remote) logging

@sleidig sleidig changed the title refactor(logging): update to latest sentry sdk and use LoggerService WIP: refactor(logging): update to latest sentry sdk and use LoggerService Dec 3, 2019
@sleidig sleidig changed the title WIP: refactor(logging): update to latest sentry sdk and use LoggerService refactor(logging): update to latest sentry sdk and use LoggerService Dec 3, 2019
.config('https://bd6aba79ca514d35bb06a4b4e0c2a21e@sentry.io/1242399')
.install();
Sentry.init({
dsn: 'https://bd6aba79ca514d35bb06a4b4e0c2a21e@sentry.io/1242399',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these values be moved to appconfig?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes it somehow very hard to catch errors during startup, as the appconfig is injected somewhere in the process. Storing the messages in some kind of queue until we initialized the client would be a bigger change... Maybe we should set up a different issue tracking this. What do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this would actually belong into the config.json ... but when I tried now I was indeed failing to get the config ready loaded while still having things cleanly separated.
I opened a separate issue for this now (#385) so that the cleaned up logging can be release already.

@sleidig sleidig merged commit 2d186d4 into master Dec 5, 2019
@sleidig sleidig deleted the improved-remote-logging branch December 5, 2019 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants