Support reading configuration through environment variables

[aldy505]

Problem Statement

Make sure we support this https://develop.sentry.dev/sdk/expected-features/environment-variables/

Solution Brainstorm

.

[linear]

GO-119

[manasa-bhagwat]

Hi @giortzisg I’d like to work on this.

Based on the SDK configuration spec my understanding is that the Go SDK should read common environment variables (e.g. SENTRY_DSN, SENTRY_RELEASE, SENTRY_ENVIRONMENT, SENTRY_SAMPLE_RATE, SENTRY_TRACES_SAMPLE_RATE, SENTRY_DEBUG) when the corresponding fields are not explicitly provided in ClientOptions.

My plan is to add environment variable fallbacks during client initialization while ensuring that explicitly provided options always take precedence over env vars.

Happy to adjust the scope depending on which variables the Go SDK should support initially.

[aldy505]

@manasa-bhagwat We appreciate your interest, but this effort is being hold-off internally. Please don't work on this for the time being.

[manasa-bhagwat]

Thanks @aldy505 for the clarification!

I'd definitely still be interested in contributing to the Go SDK or other Sentry OSS repositories.

If there are any issues in "sentry-go" (or another Sentry repo) that would be helpful for external contributors to pick up, I'd be happy to take a look.

Appreciate any pointers.

[giortzisg]

Hey @manasa-bhagwat,
Thanks for the interest. We currently don't have any really good first time issues (except this one).

Then also these might be good candidates, to also learn how errors work on the SDK, but require some aligning.

• Add Meta information to Exception Mechanism #965
• Set mechanism type to origin #1102