Closed biohazardxxx closed 3 years ago
Recent go-mssqldb(v0.10.0) might have a fix for this(https://github.com/denisenkom/go-mssqldb/pull/642)
This issue is reproduced at the SQL server with a self-signed certificate. As jjh75 mentions this issue could be fixed with an update to go-mssqldb(v0.10.0), it there any chances to have this fix in the next release?
I can confirm this issue is also present on linux and also solved for linux in the nightly build.
Relevant telegraf.conf:
System info:
Actual behavior:
Additional info:
It works ok with telegraf-1.16.1_windows_amd64
Same error with the new type of config as described on current README