-
Notifications
You must be signed in to change notification settings - Fork 523
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
Test OTEL retries works #3086
Comments
@JamesNK - Just the heads up. A change is coming for this open-telemetry/opentelemetry-dotnet#5495 It should be released tomorrow. I will update here, once the package is available with the change. |
It is available now: https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol/1.8.0 |
PR to update to 1.8.0 - #3351 |
@JamesNK - Could you try increasing the timeout period? https://github.com/open-telemetry/opentelemetry-dotnet/blob/9b246750ab76e94986fc433d5c7af046a137e477/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/OtlpExporterOptions.cs#L113-L117? How long does it try to retry? - The retries will continue until the total time does not exceed the configured timeout for each export. How many times does it retry - There is no defined # of retires, it is only controlled by the timeout period (which is max time the exporter can spend on exporting each batch). |
Thanks. I tested with a 10 second startup delay and it works with the retry env var and doesn't work without the retry env var. That means it's working as expected. 10 second timeout is fine as a default. |
Test https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol/1.8.0-beta.1 retry logic works.
Can test by delaying startup of dashboard and then ensuring that telemetry from apps is eventually correctly recorded.
The text was updated successfully, but these errors were encountered: