You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[[inputs.sqlserver]]
## Specify instances to monitor with a list of connection strings.## All connection parameters are optional.## By default, the host is localhost, listening on default port, TCP 1433.## for Windows, the user is the currently running AD user (SSO).## See https://github.com/denisenkom/go-mssqldb for detailed connection## parameters.servers = [
"Server=xxxxx.database.windows.net;Port=1433;User Id=telegraf;Password=xxxx;app name=telegraf;log=1;",
]
## This enables a specific set of queries depending on the database type. If specified, it replaces azuredb = true/false and query_version = 2## In the config file, the sql server plugin section should be repeated each with a set of servers for a specific database_type.## Possible values for database_type are ## "AzureSQLDB" ## "SQLServer"## "AzureSQLManagedInstance"database_type = "AzureSQLManagedInstance"## Optional parameter, setting this to 2 will use a new version## of the collection queries that break compatibility with the original## dashboards.## query_version = 2## If you are using AzureDB, setting this to true will gather resource utilization metrics## azuredb = true## If you would like to exclude some of the metrics queries, list them here## Possible choices:## - PerformanceCounters## - WaitStatsCategorized## - DatabaseIO## - DatabaseProperties## - CPUHistory## - DatabaseSize## - DatabaseStats## - MemoryClerk## - VolumeSpace# exclude_query = [ 'DatabaseIO' ]
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?
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
The text was updated successfully, but these errors were encountered: