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

We should be logging to stdout/stderr in development #402

Open
domharrington opened this issue Apr 20, 2022 · 3 comments
Open

We should be logging to stdout/stderr in development #402

domharrington opened this issue Apr 20, 2022 · 3 comments

Comments

@domharrington
Copy link
Member

If there are any issues with log insertion, we should be printing that out to the console when development: true

@domharrington
Copy link
Member Author

@erunion
Copy link
Member

erunion commented Aug 10, 2022

@domharrington The Node SDK is doing that but should all SDKs throw exceptions when in development mode or should we be logging these to the console instead? What about when you aren't in development mode? Should we have a configurable logfile somewhere?

@domharrington
Copy link
Member Author

domharrington commented Aug 10, 2022

These are all great questions - what do you think? I've actually removed the development flag from all of the code samples in the dashboard because we dont do a great job right now of showing development logs.

We absolutely cannot throw exceptions or halt anyone's servers if we go down, or if there's a bug in the SDK, but for things like the API key being incorrect we should probably be louder than we are currently.

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

No branches or pull requests

2 participants