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

Influxdb output does not handle integer value correctly #9120

Closed
jcdauchy-moodys opened this issue Jul 22, 2024 · 3 comments · Fixed by #9301
Closed

Influxdb output does not handle integer value correctly #9120

jcdauchy-moodys opened this issue Jul 22, 2024 · 3 comments · Fixed by #9301

Comments

@jcdauchy-moodys
Copy link

jcdauchy-moodys commented Jul 22, 2024

Bug Report

Describe the bug
If value is an integer, using Influxdb line protocol, we should suffix the value with an "i", this is not the case, so all values are sent as float

  • Steps to reproduce the problem:

create a measurement in influxdb database with a column of type integer, then push some data as integer type in fluentbit, your data will not be pushed.

Expected behavior

Screenshots

[2024/07/22 12:55:13] [error] [output:influxdb:influxdb.1] http_status=400 {"error":"partial write: field type conflict: input field "myintergerfiled" on measurement "test" is type integer, already exists as type float dropped=5"}

Your Environment

  • Version used: 2.1.7 and others
  • Configuration:
  • Environment name and version : kubernetes 1.30
  • Filters and plugins:

Influxdb output

Additional context

I tried to push a log to an influxdb measurement already created with an integer column type and it was complainging that my value is FLOAT :

@jcdauchy-moodys
Copy link
Author

I will try to fix it soon.

@Athishpranav2003
Copy link

@jcdauchy-moodys are you working on this or can i make a PR for this real quick?
I guess i understood the problem here but just need to make sure if you are working on this currently

@cosmo0920
Copy link
Contributor

Hi, I'm tried to create a patch for fixing this: #9301
Could you add a reproducible steps for this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants