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

no timestamp value #33412

Open
yoyoraso opened this issue Jun 6, 2024 · 4 comments
Open

no timestamp value #33412

yoyoraso opened this issue Jun 6, 2024 · 4 comments
Labels
bug Something isn't working exporter/kafka

Comments

@yoyoraso
Copy link

yoyoraso commented Jun 6, 2024

Component(s)

exporter/kafka

What happened?

Description

Hi I send data to reciever otlp and export by two ways (file and kafka) I can see in the file a Timestamp value and ObservedTimestamp but for the kafka I don't see any in the message only Trace ID and Span ID

Steps to Reproduce

Expected Result

Actual Result

Collector version

latest otel/opentelemetry-collector-contrib image

Environment information

Environment

kubernetes cluster on ubuntu linux

OpenTelemetry Collector configuration

receivers: 
      otlp:
        protocols:
          grpc:
            endpoint: 0.0.0.0:4317
          http:
            endpoint: 0.0.0.0:4318
    processors:
      batch:

    exporters:
      file:
        path: /tmp/otel-logfile.log      
      debug:
        verbosity: detailed      
      kafka:
        brokers:
          - ******
        topic: otel-kafka
        encoding: otlp_json
        producer:
          compression: gzip
    service:
      pipelines:
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [debug,kafka]          
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [kafka]          
      telemetry:
        logs:
          level: "debug"

Log output

No response

Additional context

No response

@yoyoraso yoyoraso added bug Something isn't working needs triage New item requiring triage labels Jun 6, 2024
Copy link
Contributor

github-actions bot commented Jun 6, 2024

Pinging code owners:

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

@frzifus
Copy link
Member

frzifus commented Jun 12, 2024

Is that the case for all kinds of signals?

I assume latest means v0.102.0?

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 atoulme removed the needs triage New item requiring triage label Oct 2, 2024
@atoulme
Copy link
Contributor

atoulme commented Oct 2, 2024

Can you please give us a reproducible test case?

@github-actions github-actions bot removed the Stale label Oct 3, 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/kafka
Projects
None yet
Development

No branches or pull requests

3 participants