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

Docker plugin + InfluxDB 2.0: type mismatch #8570

Closed
Jamesits opened this issue Dec 16, 2020 · 1 comment · Fixed by #10711
Closed

Docker plugin + InfluxDB 2.0: type mismatch #8570

Jamesits opened this issue Dec 16, 2020 · 1 comment · Fixed by #10711
Labels
area/influxdb bug unexpected problem or unintended behavior

Comments

@Jamesits
Copy link

Relevant telegraf.conf:

[[inputs.docker]]
  endpoint = "unix:///var/run/docker.sock"
  gather_services = true
  source_tag = true
  timeout = "5s"
  perdevice = true
  total = true

System info:

  • CentOS 7.9
  • Telegraf 1.16.1 (git: HEAD 292e285)
  • Docker version 20.10.0, build 7287ab3

Docker

N/A

Steps to reproduce:

  1. Enable Telegraf Docker plugin and a InfluxDB v2 output plugin
  2. Wait a while for the docker_swarm series to be created
  3. Enable Docker Swarm mode on the host

Expected behavior:

Telegraf should be able to write new data to influxdb.

Actual behavior:

E! [agent] Error writing to outputs.influxdb_v2: 500 Internal Server Error: internal error: unexpected error writing points to database: partial write: field type conflict: input field "tasks_desired" on measurement "docker_swarm" is type integer, already exists as type unsigned dropped=7

Additional info:

N/A

@Jamesits Jamesits added the bug unexpected problem or unintended behavior label Dec 16, 2020
@sspaink
Copy link
Contributor

sspaink commented Feb 22, 2022

Thank you for reporting this issue, I created a PR to resolve it: #10711

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/influxdb bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants