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

Why trace clickhouse exporter always shows "Exporting Failed: The column Timestamp is not present" #32886

Closed
hueiyuan opened this issue May 7, 2024 · 4 comments
Labels
bug Something isn't working exporter/clickhouse question Further information is requested

Comments

@hueiyuan
Copy link

hueiyuan commented May 7, 2024

Component(s)

exporter/clickhouse

Describe the issue you're reporting

Hi everyone,
We try to export Otel trace data to clickhouse, but we found that the collector sometimes shows "Exporting Failed: The column Timestamp is not present". And after retry, which can flush to clickhouse successfully.
Does anyone have idea to solve it? Thank you.

Error Message Example

│ 2024-05-07T06:56:16.602Z    info    exporterhelper/retry_sender.go:118    Exporting failed. Will retry the request after interval.    {"kind": "exporter", "data_type": " │
│ traces", "name": "clickhouse/xxxx", "error": "PrepareContext:column Timestamp is not present in the table trace_table", "interval": "4.155902648s"} │

Version

  • otel collector: 0.99.0
  • clickhouse-go: 2.23
@hueiyuan hueiyuan added the needs triage New item requiring triage label May 7, 2024
Copy link
Contributor

github-actions bot commented May 7, 2024

Pinging code owners:

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

@SpencerTorres
Copy link
Member

I have a few questions/ideas on why this might be happening:

  • Is it possible that the export batch is trying to run before the table has been created? This would only happen on first start if otel_traces doesn't exist. It is recommended to manually create the required tables before running the exporter.
  • Are you running any other table/database changes in the background? If some kind of schema migration tool is running, there could be a case where Timestamp is temporarily not present on the otel_traces table.
  • Are you running in any kind of clustered setup where the INSERT would be routed to a destination that does not have the trace table fully created?
  • Did otel_traces exist before you ran the exporter? In this case, it will rely on the existing table instead of overwriting it, which means you will need to ensure the schema you are using is compatible with the latest exporter version.

I noticed you are using trace_table (according to the logs). While this table may exist if you created it, it might not contain the correct columns. Please refer to the default_ddl folder of the ClickHouse exporter for a reference of what DDL is run automatically. In this case, the trace DDL would be relevant.

Copy link
Contributor

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.

@atoulme
Copy link
Contributor

atoulme commented Oct 2, 2024

@hueiyuan I am going to close this issue as inactive. Please reopen if more information is needed.

@atoulme atoulme closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working exporter/clickhouse question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants