-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Collector sending queue value not getting reflected #37445
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hey! Thanks for submitting an issue, this info is helpful The most recent change to this area that I can recall is #34176, but this simply follows the defaults. It calls this which sets the current default to It all seems to be correct, I wonder if it's reporting it incorrectly to the metrics somehow? We can run it through a debugger to find out. I see there's also a field called |
Hi @SpencerTorres, Thank you for your response let me try that and get back to you. |
Hi @SpencerTorres, tried by keeping the enabled : true still it is not getting reflected any other way to increase the queue or any suggestions. |
Component(s)
exporter/clickhouse
What happened?
Description
The sending_queue.queue_size configuration was set to 10000 for the OpenTelemetry Collector’s ClickHouse exporter. However, when checking the metrics, the queue size appears to be set to the default value of 1000. This discrepancy suggests that the configured value is not being applied as expected.
• Operator Version: 0.68.1
• Collector Image: otel/opentelemetry-collector-contrib:0.109.0
Steps to Reproduce
Steps to Reproduce
1. Deploy an OpenTelemetry Collector using the following configuration:
exporters: clickhouse: endpoint: tcp://{{.Values.endpoints }} username: {{.Values.db_user | quote }} database: {{.Values.database }} password: {{.Values.db_pw | quote }} logs_table_name: {{ .Values.logtable }} traces_table_name: otel_traces create_schema: true ttl: 12h timeout: 10s sending_queue: queue_size: 10000 retry_on_failure: enabled: true initial_interval: 5s max_interval: 30s max_elapsed_time: 300s
2. Verify that the deployment uses:
• OpenTelemetry Operator: 0.68.1
• Collector Image: otel/opentelemetry-collector-contrib:0.109.0
3. Monitor the metrics using the /metrics endpoint or Prometheus.
4. Look for the exporter_send_queue_size metric.
Expected Result
The exporter_send_queue_size metric should reflect the configured value of 10000.
Actual Result
The exporter_send_queue_size metric shows the default value of 1000, indicating that the configuration was not applied.
Collector version
v0.109.0
Environment information
Environment
OS: AWS EKS (Managed Kubernetes Service)
Cluster Version: 1.30
OpenTelemetry Collector configuration
Log output
Additional context
In argocd I am able to see the configuration as 10000 but in metrics it is 1000(default value).
The text was updated successfully, but these errors were encountered: