-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Failed to connect/Error was 'unsupported scheme #8231
Comments
Can you the full config for your |
Here ya go @sjwang90
|
That error message doesn't correspond this problem, but at first glance the Can you run check the environment variable you set for your URL. Here's some documentation around it that may help. |
Hey @coolblknerd just checking if this is still a problem. Closing this issue for now. Please reach out to us in our Community Slack or Community Page as it'll be a better place to get this question answered. |
I am getting this issue as well. here is my /etc/telegraf/telegraf.d/outputs.influxdb.conf
Here is my /etc/default/telegraf
then my /etc/telegraf/telegraf.d/inputs.pihole.conf for good measure
print of my
Another note, when I run telegraf --test, it is meant to pull from the telegraf.d and essentially make one large conf file correct? That is what I read here #6334 |
I've been trying to configure the telegraf agent on some nodes however I can't get the agent to pick up my URL value that's using a environment variable. I understand that 1.11 introduced the ${} syntax, however, whether I uses the new or old syntax, the environment variable isn't getting picked up.
Relevant telegraf.conf:
System info:
Telegraf: 1.15.3
Ubuntu 20.04 LTS
Steps to reproduce:
Expected behavior:
Expect Telegraf to connect to the given InfluxDB URI without any errors.
Actual behavior:
Receiving "[agent] Failed to connect to [outputs.influxdb], retrying in 15s, error was 'unsupported scheme ["$INFLUXDB_URI"]: "
Additional info:
The text was updated successfully, but these errors were encountered: