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

Error - configuration specified the fields ["__something__"], but they weren't used #8417

Closed
Trovalo opened this issue Nov 16, 2020 · 0 comments · Fixed by #8419
Closed

Error - configuration specified the fields ["__something__"], but they weren't used #8417

Trovalo opened this issue Nov 16, 2020 · 0 comments · Fixed by #8419
Assignees
Labels
bug unexpected problem or unintended behavior

Comments

@Trovalo
Copy link
Collaborator

Trovalo commented Nov 16, 2020

Relevant telegraf.conf:

# Collect statistics about itself
[[inputs.internal]]
  ## If true, collect telegraf memory stats.
  # collect_memstats = true
  [inputs.internal.tags]
    telegraf_instance = "Telegraf Gateway"

Here is the error I get

2020-11-16T15:53:50Z E! [telegraf] Error running agent: Error loading config file configuration\gateway\telegraf.d\input_internal.conf: plugin inputs.internal: line 3: configuration specified the fields ["tags"], but they weren't used

System info:

  • Windows Server
  • Equivalent to Telegraf Nightly (I usually make my own build)

Steps to reproduce:

  • Specify some additional static tags in an input plugin using the [inputs._inputname_.tags]
    In my case I've just used the internal plugin, but I think the issue present itself on any plugin.

Expected behavior:

The configuration is valid and everything runs

Actual behavior:

an error happens

Additional info:

@Trovalo Trovalo added the bug unexpected problem or unintended behavior label Nov 16, 2020
@ssoroka ssoroka self-assigned this Nov 16, 2020
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants