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

Line Protocol generated by influxDB exporter seems to be incorrect #33444

Open
yasha145 opened this issue Jun 10, 2024 · 4 comments
Open

Line Protocol generated by influxDB exporter seems to be incorrect #33444

yasha145 opened this issue Jun 10, 2024 · 4 comments

Comments

@yasha145
Copy link

yasha145 commented Jun 10, 2024

Component(s)

exporter/influxdb

What happened?

Description

The line protocol generated by influxDB exporter has following issues:
String values are not enclosed by double quotes because all the data is been mapped to tags set instead of to fields set.

Because of above issue, the influxDB UI (hosted in localhost 8086) is not displaying any data as UI needs data to be in fields set while data and measurements is been displayed via influxQL.

Expected Result

SP-Srvrmon File\ Start\ Time="20240115T1958-00000121-20min",Thread\ No.=155909,epochthreadEnd=1705348627,epochthreadStart=1705347444,otel.library.name="SP-Srvrmon",psSessionThread.DB2\ Fetch\ Prep.MaxTime=0.004,psSessionThread.DB2\ Fetch\ Prep.MinTime=0,psSessionThread.DB2\ Fetch\ Prep.totTime=0.006,count=0

Actual Result

SP-Srvrmon,File\ Start\ Time=20240115T1958-00000121-20min,Thread\ No.=155909,epochthreadEnd=1705348627,epochthreadStart=1705347444,otel.library.name=SP-Srvrmon,psSessionThread.DB2\ Fetch\ Prep.MaxTime=0.004,psSessionThread.DB2\ Fetch\ Prep.MinTime=0,psSessionThread.DB2\ Fetch\ Prep.totTime=0.006 count=0 0

Collector version

v0.95.0

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

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

Pinging code owners:

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

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

@jacobmarble please review as code owner

Copy link
Contributor

github-actions bot commented Dec 3, 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.

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

2 participants