-
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
postgresql / postgresql_extensible: db
label (dbname) changed
#14007
Comments
The database name should either be postgres or the value from a correctly parsed dsn. fixes: influxdata#14007
This whole logic is a bit of a mess :\ I think I have restored the behavior given that you are setting the output address, we should instead return postgres. I have updated the test case and put up #14007. |
@hloeung hoping to land this with Monday's v1.27.2. Would you have time to confirm the new diff restores the previous functionality? Thanks! |
Unfortunately, I'm going away this long weekend without access to work stuff, public holiday here in AU. Happy to test it Tuesday when I return, if you can wait? Thanks for your time. |
No worries, we can grab it in the next point release. Enjoy your holiday! |
@powersj, tested package looks good to me:
So |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.28.1, Ubuntu 20.04.6 LTS
Docker
No response
Steps to reproduce
...
Expected behavior
Using an older telegraf, 1.25.0, we get this:
Actual behavior
Using a newer telegraf, 1.28.1 with patches from Josh per #13965), we now get this:
Additional info
It looks like another fallout from #13602 where the
db
label was oncepostgres
is now changed:The text was updated successfully, but these errors were encountered: