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

CrateDB output plugin fails with memory input plugin #4110

Closed
nomicode opened this issue May 5, 2018 · 0 comments · Fixed by #4117
Closed

CrateDB output plugin fails with memory input plugin #4110

nomicode opened this issue May 5, 2018 · 0 comments · Fixed by #4117
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Milestone

Comments

@nomicode
Copy link

nomicode commented May 5, 2018

Bug report

Relevant telegraf.conf:

# Read metrics about memory usage
[[inputs.mem]]
  # no configuration

System info:

CrateDB 2.3

tested failing with two versions of Telegraf

installed via Homebrew on macOS 10.13.4:

$ telegraf --version
Telegraf v1.6.1 (git: unknown unknown)

installed via go get on macOS 10.13.4:

$ ./telegraf --version
Telegraf v1.7.0~d96bcac3 (git: master d96bcac3)

Steps to reproduce:

  1. telegraf --input-filter mem --output-filter cratedb config > telegraf.conf
  2. configure the CrateDB connection string
  3. telegraf --config telegraf.conf

Expected behavior:

Telegraf runs with no errors, and the CrateDB table is created and populated

Actual behavior:

repeated messages like this:

2018-05-05T20:51:42Z E! Error writing to output [cratedb]: unexpected type: uint64: 0x16618f000

the table is created, but no records are written to CrateDB

Additional info:

this does not happen with the cpu input plugin

I have not tested any other plugins

@danielnelson danielnelson added this to the 1.6.2 milestone May 7, 2018
@danielnelson danielnelson added bug unexpected problem or unintended behavior regression something that used to work, but is now broken labels May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants