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

External output plugin - configuration not applied #13488

Closed
muhlba91 opened this issue Jun 23, 2023 · 2 comments
Closed

External output plugin - configuration not applied #13488

muhlba91 opened this issue Jun 23, 2023 · 2 comments
Labels
bug unexpected problem or unintended behavior waiting for response waiting for response from contributor

Comments

@muhlba91
Copy link
Contributor

muhlba91 commented Jun 23, 2023

Relevant telegraf.conf

[[outputs.execd]]
   command = [ "/plugins/bin/firehose/telegraf-output-kinesis-data-firehose", "-config", "/plugins/config/plugin.conf" ]
   restart_delay = "10s"
   ignore_serialization_error = true
   data_format = "influx"
[[outputs.firehose]]
  region = "${AWS_REGION}"
  access_key = "${AWS_ACCESS_KEY_ID}"
  secret_key = "${AWS_SECRET_ACCESS_KEY}"

  streamname = "${FIREHOSE_DELIVERY_STREAM}"

  batchsize = 500

  [format]
    flatten = true
    normalize_keys = true
    name_key_rename = "unit"
    timestamp_as_rfc3339 = false
    timestamp_units = "1ms"

Logs from Telegraf

This is kind of a reopen of https://github.com/influxdata/telegraf/issues/8272.

System info

Telegraf 1.27.1, Docker Image

Docker

No response

Steps to reproduce

Use an execd output plugin with nested configuration.

Expected behavior

The specified configuration to be applied in the output plugin.
The contents are read though.

Actual behavior

The specified configuration in the file is not applied.

Additional info

N/A

@muhlba91 muhlba91 added the bug unexpected problem or unintended behavior label Jun 23, 2023
powersj added a commit to powersj/telegraf that referenced this issue Jun 23, 2023
@powersj
Copy link
Contributor

powersj commented Jun 23, 2023

Hi,

The specified configuration in the file is not applied.

I need more information... because based on what you are shown you have not described how or why you think a config was not passed through.

You have a bunch of environment variables declared, which is usually a source of issues depending on how people launch telegraf. If you replace those with real values, does everything work?

As an example that values are passed through, you can use the following config to show that arguments are in fact passed on:

[[outputs.execd]]
   command = [ "echo", "foobar" ]
   restart_delay = "10s"
   ignore_serialization_error = true
   data_format = "influx"

which results in errors, but you do get:

2023-06-23T21:45:43Z I! [outputs.execd] foobar
2023-06-23T21:45:43Z E! [outputs.execd] Process /usr/bin/echo exited: <nil>

Finally, I wrote a test to validate that the config is loaded: 698a822 which passes.

@powersj powersj added the waiting for response waiting for response from contributor label Jun 23, 2023
@telegraf-tiger
Copy link
Contributor

telegraf-tiger bot commented Jul 8, 2023

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you!

@telegraf-tiger telegraf-tiger bot closed this as completed Jul 8, 2023
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 waiting for response waiting for response from contributor
Projects
None yet
Development

No branches or pull requests

2 participants