We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As suggested in #195 (comment), I have added quarkus.otel.bsp.schedule.delay in https://github.com/quarkiverse/quarkus-opentelemetry-exporter/blob/main/quarkus-opentelemetry-exporter-azure/integration-tests/src/main/resources/application.properties
quarkus.otel.bsp.schedule.delay
However, the quarkus.otel.bsp.schedule.delay value seems to have no effect.
quarkus-opentelemetry-exporter-azure does not seem to have its own batch.
quarkus-opentelemetry-exporter-azure
So, quarkus.otel.bsp.schedule.delay may not work for the Azure exporter and other exporters.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As suggested in #195 (comment), I have added
quarkus.otel.bsp.schedule.delayin https://github.com/quarkiverse/quarkus-opentelemetry-exporter/blob/main/quarkus-opentelemetry-exporter-azure/integration-tests/src/main/resources/application.propertiesHowever, the
quarkus.otel.bsp.schedule.delayvalue seems to have no effect.quarkus-opentelemetry-exporter-azuredoes not seem to have its own batch.So,
quarkus.otel.bsp.schedule.delaymay not work for the Azure exporter and other exporters.The text was updated successfully, but these errors were encountered: