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

[otlp] Update README for UseOtlpExporter & new experimental flag #5452

Merged
merged 17 commits into from
Mar 21, 2024
Prev Previous commit
Next Next commit
Lint.
  • Loading branch information
CodeBlanch committed Mar 19, 2024
commit 452c40b0c3ca5abc14a8a53a723f36ae8469b6fa
Original file line number Diff line number Diff line change
Expand Up @@ -628,7 +628,7 @@ want to solicit feedback from the community.
* All signals

* `OTEL_DOTNET_EXPERIMENTAL_OTLP_ENABLE_INMEMORY_RETRY`
Copy link
Member

Choose a reason for hiding this comment

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

@vishweshbankwar I have questions regarding the name - does it mean later there will be something like "OTLP_ENABLE_ONDISK_RETRY? What's the thinking which leads to the current name instead of OTEL_DOTNET_EXPERIMENTAL_OTLP_ENABLE_RETRY`?

Copy link
Member

Choose a reason for hiding this comment

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

does it mean later there will be something like "OTLP_ENABLE_ONDISK_RETRY

That was the thinking. Wanted to have decoupled experimental environment variables.

When we move to stable, I would like it to be OTEL_DOTNET_OTLP_ENABLE_RETRY and define possible values for it like inmemory and disk.


When set to `true`, it enables in-memory retry for transient errors
encountered while sending telemetry.

Expand Down