-
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
Fix rethinkdb plugin to work with actual database and actual authorization protocol #2963
Conversation
…that requires username,password authorization and Handshake protocol v1.0
Previous PR - #2959 |
Issue related - #2958 |
code seems working - it passed your CI tests, and it works ok on my local machine |
What do you think about my suggestion to add username and password options to the plugin, and then use the old handshake method if authkey is set in the url, otherwise use the username and password? I'd like to move away from the url encoded userinfo since it can be tricky to escape special characters, makes logging difficult, and its use is deprecated in rfc3986. |
i think DSL names is best approach, universal - it is possible to monitor servers with different versions and different credentials easily:
so this approach allows to monitor both old and new versions on rethinkdb, and is backward compatible with approach being used before. anyway, for me i'd like to use approach i made in PR or in my fork - because it works for me maybe servers have to be an array of hashes consisting of username, password, hostname, port, authkey, protocol to use |
Oh yeah, my way is problematic with multiple servers and we don't want to make breaking changes to the config for this, so lets just go with this. Perhaps in the future we can have one server per plugin instance. |
# ## | ||
# ## If you use older versions of rethinkdb (<2.2) with auth_key, protocol | ||
# ## have to be named "rethinkdb". | ||
# servers = ["rethinkdb://username:auth_key@127.0.0.1:28015"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the sampleConfig, don't have the header and remove the top level comment #. Test out how it looks with telegraf --input-filter rethinkdb --output-filter none config
thx! |
Thanks so much! |
Allow rethinkdb input plugin to work with RethinkDB 2.3.5+ databases that requires username,password authorization and Handshake protocol v1.0 * remove top level header not required in sample config * remove top level header not required in sample config
Allow rethinkdb input plugin to work with RethinkDB 2.3.5+ databases that requires username,password authorization and Handshake protocol v1.0 * remove top level header not required in sample config * remove top level header not required in sample config
Required for all PRs: