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

[exporter/clickhouse] [Usage][BugReport] Data is lost while using collector. #26465

Closed
mioyui88 opened this issue Aug 27, 2023 · 10 comments
Closed

Comments

@mioyui88
Copy link

mioyui88 commented Aug 27, 2023

Describe the bug
I'm using collector to gather data from multi agents. Collector executing insert SQL into ClickHouse, and error like 'context deadline exceeded'.

Steps to reproduce
I use collector to gather data.
Collector executes insert into ClickHouse.

What did you expect to see?
SQL insertion successes.

What did you see instead?
error report like 'context deadline exceeded'.

What version did you use?
signoz-otel-collector: v0.76.2

What config did you use?
I will paste later.

Environment
OS: Centos 3.10.0
Compiler(if manually compiled): go 17.2

Additional context

@mioyui88 mioyui88 added the bug Something isn't working label Aug 27, 2023
@mioyui88
Copy link
Author

Mirror Issue Link: SigNoz/signoz-otel-collector#170

@mioyui88
Copy link
Author

Is there any relationship between the error and ClickHouse index?

@mx-psi
Copy link
Member

mx-psi commented Aug 28, 2023

error report like 'context deadline exceeded'.

This usually comes from a timeout. What Collector components are you using? Are you perhaps using the ClickHouse Exporter?

@mioyui88
Copy link
Author

mioyui88 commented Sep 5, 2023

error report like 'context deadline exceeded'.

This usually comes from a timeout. What Collector components are you using? Are you perhaps using the ClickHouse Exporter?

I check the Clickhouse to the different Clickhouse instance, then the insert failed disappear, so I think maybe is the clickhouse instance problem.

@mx-psi mx-psi transferred this issue from open-telemetry/opentelemetry-collector Sep 5, 2023
@mx-psi mx-psi changed the title [Usage][BugReport] Data is lost while using collector. [exporter/clickhouse] [Usage][BugReport] Data is lost while using collector. Sep 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Sep 5, 2023

Pinging code owners for exporter/clickhouse: @hanjm @dmitryax @Frapschen. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@mx-psi
Copy link
Member

mx-psi commented Sep 5, 2023

error report like 'context deadline exceeded'.

This usually comes from a timeout. What Collector components are you using? Are you perhaps using the ClickHouse Exporter?

I check the Clickhouse to the different Clickhouse instance, then the insert failed disappear, so I think maybe is the clickhouse instance problem.

Alright, I am going to label this as 'waiting for author' until you verify this. I also transferred this to contrib and labeled it under the clickhouse exporter.

Copy link
Contributor

github-actions bot commented Nov 6, 2023

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 6, 2023
@hanjm
Copy link
Member

hanjm commented Nov 9, 2023

please provide and check the collector full config and more log at debug level. batch_size, send_timeout.

please check the clickhouse endpoint work. (curl endpoint it will response some text)

please check the collector and clickhouse resource usage( cpu mem disk)

@github-actions github-actions bot removed the Stale label Nov 9, 2023
Copy link
Contributor

github-actions bot commented Jan 9, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 9, 2024
Copy link
Contributor

github-actions bot commented Mar 9, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants