-
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
inputs/mongodb not parsing configs #2888
Comments
Possible workaround is to use the mongodb:// uri scheme. |
Seems to be working OK using mongodb:// uri now with 1.3.0 |
And likewise with 1.3.1 |
I'm going to reopen since this should still be fixed. |
This appears to be caused by a change in go 1.8: golang/go#19297. They are not going to fix it since it was originally a bug and so I'll just change our default urls. |
Same bug in the leofs plugin |
Should we fix this with documentation and reference the issue? |
I did a combination of documentation and code. The old method should still work for now but it prompts you to use a url with scheme. For mongodb use |
Bug report
Up to 1.2.1 this was working; in 1.3.0 and 1.3.1, getting error reading config.
Relevant telegraf.conf:
See https://gist.github.com/Jaff/3a2024afaf44b9b5a448090f46a94fc8
System info:
telegraf 1.3.0, 1.3.1 on Ubuntu 14.04.4 (x86_64)
[Include Telegraf version, operating system name, and other relevant details]
Steps to reproduce:
Expected behavior:
telegraf will collect data from mongodb and output to graphite log
Actual behavior:
telegraf unable to connect to mongodb
Additional info:
logs contain:
2017-06-05T20:56:30Z E! Error in plugin [inputs.mongodb]: Unable to parse to address '127.0.0.1:27017': parse 127.0.0.1:27017: first path segment in URL cannot contain colon
[Include gist of relevant config, logs, etc.]
Feature Request
Opening a feature request kicks off a discussion.
Proposal:
Current behavior:
Desired behavior:
Use case: [Why is this important (helps with prioritizing requests)]
The text was updated successfully, but these errors were encountered: