-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/clickhouse] exported data is missing, the amount is not match #33923
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello! Thanks for the detailed issue and sample data. Are the results correct with a different exporter? If you wrote the lines to a file, would they match up in that case? I want to make sure this isn't an issue with ClickHouse. Also it looks like you're counting from metrics. You should check to confirm that the metrics are not being grouped at any point. Possible points where they could be summed/grouped:
Also check the exporter logs to see if everything is being exported correctly (no dropped/failed batches). |
Hi, @Lincyaw Help me add the below config to your otel config:
Please check the metrics related to receiver and exporter metrics from |
Component(s)
exporter/clickhouse
What happened?
Description
I use opentelemetry-collector-contrib:0.104.0 version, with clickhouse exporter. But the data amount is mismatch compared to the reported data.
Steps to Reproduce
Use the following docker compose file to start a instance
This otel config is used, place these two files together, then run
docker compose up
Then, use a golang code, to send data:
The
data.pb
is attached in dropbox, please download it.go.mod is:
Then run the go file. The data will be sent to the otel collector, then to clickhouse.
Expected Result
The amount should exactly equal to 1380344.
Actual Result
It is unstable. Sometimes less, sometimes normal
Collector version
0.104.0
Environment information
Environment
OS: debian sid
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: