Telegraf: SQL Server input plug-in erorr when using "database_type" config switch in telegraf.

[johndnlightnit]

Relevant telegraf.conf:

# Telegraf Configuration
#
# Telegraf is entirely plugin driven. All metrics are gathered from the
# declared inputs, and sent to the declared outputs.
#
# Plugins must be declared in here to be active.
# To deactivate a plugin, comment out the name and any variables.
#
# Use 'telegraf -config telegraf.conf -test' to see what metrics a config
# file would generate.
#
# Environment variables can be used anywhere in this config file, simply surround
# them with ${}. For strings the variable must be within quotes (ie, "${STR_VAR}"),
# for numbers and booleans they should be plain (ie, ${INT_VAR}, ${BOOL_VAR})


# Global tags can be specified here in key="value" format.
[global_tags]
  # dc = "us-east-1" # will tag all metrics with dc=us-east-1
  # rack = "1a"
  ## Environment variables can be used as tags, and throughout the config file
  # user = "$USER"


# Configuration for telegraf agent
[agent]
  ## Default data collection interval for all inputs
  interval = "10s"
  ## Rounds collection interval to 'interval'
  ## ie, if interval="10s" then always collect on :00, :10, :20, etc.
  round_interval = true

  ## Telegraf will send metrics to outputs in batches of at most
  ## metric_batch_size metrics.
  ## This controls the size of writes that Telegraf sends to output plugins.
  metric_batch_size = 1000

  ## Maximum number of unwritten metrics per output.  Increasing this value
  ## allows for longer periods of output downtime without dropping metrics at the
  ## cost of higher maximum memory usage.
  metric_buffer_limit = 10000

  ## Collection jitter is used to jitter the collection by a random amount.
  ## Each plugin will sleep for a random time within jitter before collecting.
  ## This can be used to avoid many plugins querying things like sysfs at the
  ## same time, which can have a measurable effect on the system.
  collection_jitter = "0s"

  ## Default flushing interval for all outputs. Maximum flush_interval will be
  ## flush_interval + flush_jitter
  flush_interval = "10s"
  ## Jitter the flush interval by a random amount. This is primarily to avoid
  ## large write spikes for users running a large number of telegraf instances.
  ## ie, a jitter of 5s and interval 10s means flushes will happen every 10-15s
  flush_jitter = "0s"

  ## By default or when set to "0s", precision will be set to the same
  ## timestamp order as the collection interval, with the maximum being 1s.
  ##   ie, when interval = "10s", precision will be "1s"
  ##       when interval = "250ms", precision will be "1ms"
  ## Precision will NOT be used for service inputs. It is up to each individual
  ## service input to set the timestamp at the appropriate precision.
  ## Valid time units are "ns", "us" (or "µs"), "ms", "s".
  precision = ""

  ## Log at debug level.
  # debug = false
  ## Log only error level messages.
  # quiet = false

  ## Log target controls the destination for logs and can be one of "file",
  ## "stderr" or, on Windows, "eventlog".  When set to "file", the output file
  ## is determined by the "logfile" setting.
  logtarget = "file"

  ## Name of the file to be logged to when using the "file" logtarget.  If set to
  ## the empty string then logs are written to stderr.
  logfile = "C:\\Program Files\\telegraf\\telegraf.log"

  ## The logfile will be rotated after the time interval specified.  When set
  ## to 0 no time based rotation is performed.  Logs are rotated only when
  ## written to, if there is no log activity rotation may be delayed.
  logfile_rotation_interval = "2d"

  ## The logfile will be rotated when it becomes larger than the specified
  ## size.  When set to 0 no size based rotation is performed.
  logfile_rotation_max_size = "100MB"

  ## Maximum number of rotated archives to keep, any older logs are deleted.
  ## If set to -1, no archives are removed.
  # logfile_rotation_max_archives = 5

  ## Override default hostname, if empty use os.Hostname()
  hostname = ""
  ## If set to true, do no set the "host" tag in the telegraf agent.
  omit_hostname = false


###############################################################################
#                            OUTPUT PLUGINS                                   #
###############################################################################



# Configuration for sending metrics to InfluxDB
[[outputs.influxdb]]
  ## The full HTTP or UDP URL for your InfluxDB instance.
  ##
  ## Multiple URLs can be specified for a single cluster, only ONE of the
  ## urls will be written to each interval.
  # urls = ["unix:///var/run/influxdb.sock"]
  # urls = ["udp://127.0.0.1:8089"]
  # urls = ["http://127.0.0.1:8086"]
  urls = ["http://192.168.149.70:8086"]


  ## The target database for metrics; will be created as needed.
  database = "mydb"

  ## If true, no CREATE DATABASE queries will be sent.  Set to true when using
  ## Telegraf with a user without permissions to create databases or when the
  ## database already exists.
  skip_database_creation = false


  ## The value of this tag will be used to determine the database.  If this
  ## tag is not set the 'database' option is used as the default.
  # database_tag = ""

  ## If true, the 'database_tag' will not be included in the written metric.
  # exclude_database_tag = false


  ## Name of existing retention policy to write to.  Empty string writes to
  ## the default retention policy.  Only takes effect when using HTTP.
  # retention_policy = ""

  ## The value of this tag will be used to determine the retention policy.  If this
  ## tag is not set the 'retention_policy' option is used as the default.
  # retention_policy_tag = ""

  ## If true, the 'retention_policy_tag' will not be included in the written metric.
  # exclude_retention_policy_tag = false

  ## Write consistency (clusters only), can be: "any", "one", "quorum", "all".
  ## Only takes effect when using HTTP.
  # write_consistency = "any"

  ## Timeout for HTTP messages.
  # timeout = "5s"

  ## HTTP Basic Auth
  # username = "telegraf"
  # password = "metricsmetricsmetricsmetrics"

  ## HTTP User-Agent
  # user_agent = "telegraf"

  ## UDP payload size is the maximum packet size to send.
  # udp_payload = "512B"

  ## Optional TLS Config for use on HTTP connections.
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"
  ## Use TLS but skip chain & host verification
  insecure_skip_verify = true

  ## HTTP Proxy override, if unset values the standard proxy environment
  ## variables are consulted to determine which proxy, if any, should be used.
  # http_proxy = "http://corporate.proxy:3128"

  ## Additional HTTP headers
  # http_headers = {"X-Special-Header" = "Special-Value"}

  ## HTTP Content-Encoding for write request body, can be set to "gzip" to
  ## compress body or "identity" to apply no encoding.
  # content_encoding = "identity"

  ## When true, Telegraf will output unsigned integers as unsigned values,
  ## i.e.: "42u".  You will need a version of InfluxDB supporting unsigned
  ## integer values.  Enabling this option will result in field type errors if
  ## existing data has been written.
  # influx_uint_support = false

# # Configuration for sending metrics to InfluxDB
# [[outputs.influxdb_v2]]
#   ## The URLs of the InfluxDB cluster nodes.
#   ##
#   ## Multiple URLs can be specified for a single cluster, only ONE of the
#   ## urls will be written to each interval.
#   ##   ex: urls = ["https://us-west-2-1.aws.cloud2.influxdata.com"]
#   urls = ["http://127.0.0.1:9999"]
#
#   ## Token for authentication.
#   token = ""
#
#   ## Organization is the name of the organization you wish to write to; must exist.
#   organization = ""
#
#   ## Destination bucket to write into.
#   bucket = ""
#
#   ## The value of this tag will be used to determine the bucket.  If this
#   ## tag is not set the 'bucket' option is used as the default.
#   # bucket_tag = ""
#
#   ## If true, the bucket tag will not be added to the metric.
#   # exclude_bucket_tag = false
#
#   ## Timeout for HTTP messages.
#   # timeout = "5s"
#
#   ## Additional HTTP headers
#   # http_headers = {"X-Special-Header" = "Special-Value"}
#
#   ## HTTP Proxy override, if unset values the standard proxy environment
#   ## variables are consulted to determine which proxy, if any, should be used.
#   # http_proxy = "http://corporate.proxy:3128"
#
#   ## HTTP User-Agent
#   # user_agent = "telegraf"
#
#   ## Content-Encoding for write request body, can be set to "gzip" to
#   ## compress body or "identity" to apply no encoding.
#   # content_encoding = "gzip"
#
#   ## Enable or disable uint support for writing uints influxdb 2.0.
#   # influx_uint_support = false
#
#   ## Optional TLS Config for use on HTTP connections.
#   # tls_ca = "/etc/telegraf/ca.pem"
#   # tls_cert = "/etc/telegraf/cert.pem"
#   # tls_key = "/etc/telegraf/key.pem"
#   ## Use TLS but skip chain & host verification
#   # insecure_skip_verify = false


###############################################################################
#                            INPUT PLUGINS                                    #
###############################################################################


# Windows Performance Counters plugin.
# These are the recommended method of monitoring system metrics on windows,
# as the regular system plugins (inputs.cpu, inputs.mem, etc.) rely on WMI,
# which utilize more system resources.
#
# See more configuration examples at:
#   https://github.com/influxdata/telegraf/tree/master/plugins/inputs/win_perf_counters

[[inputs.win_perf_counters]]
  [[inputs.win_perf_counters.object]]
    # Processor usage, alternative to native, reports on a per core.
    ObjectName = "Processor"
    Instances = ["*"]
    Counters = [
      "% Idle Time",
      "% Interrupt Time",
      "% Privileged Time",
      "% User Time",
      "% Processor Time",
      "% DPC Time",
    ]
    Measurement = "win_cpu"
    # Set to true to include _Total instance when querying for all (*).
    IncludeTotal=true

  [[inputs.win_perf_counters.object]]
    # Disk times and queues
    ObjectName = "LogicalDisk"
    Instances = ["*"]
    Counters = [
      "% Idle Time",
      "% Disk Time",
      "% Disk Read Time",
      "% Disk Write Time",
      "% Free Space",
      "Current Disk Queue Length",
      "Free Megabytes",
    ]
    Measurement = "win_disk"
    # Set to true to include _Total instance when querying for all (*).
    #IncludeTotal=false


[[inputs.win_perf_counters.object]]
# Processor usage, alternative to native, reports on a per core.
ObjectName = "Process"
Instances = ["*"]
Counters = ["Elapsed Time", "% Processor Time"]
Measurement = "win_services"


  [[inputs.win_perf_counters.object]]
    ObjectName = "PhysicalDisk"
    Instances = ["*"]
    Counters = [
      "Disk Read Bytes/sec",
      "Disk Write Bytes/sec",
      "Current Disk Queue Length",
      "Disk Reads/sec",
      "Disk Writes/sec",
      "% Disk Time",
      "% Disk Read Time",
      "% Disk Write Time",
      "Avg. Disk sec/Read",
      "Avg. Disk sec/Write",
      "Avg. Disk sec/Transfer",
    ]
    Measurement = "win_diskio"

  [[inputs.win_perf_counters.object]]
    ObjectName = "Network Interface"
    Instances = ["*"]
    Counters = [
      "Bytes Received/sec",
      "Bytes Sent/sec",
      "Packets Received/sec",
      "Packets Sent/sec",
      "Packets Received Discarded",
      "Packets Outbound Discarded",
      "Packets Received Errors",
      "Packets Outbound Errors",
    ]
    Measurement = "win_net"

  [[inputs.win_perf_counters.object]]
    ObjectName = "System"
    Counters = [
      "Context Switches/sec",
      "System Calls/sec",
      "Processor Queue Length",
      "System Up Time",
    ]
    Instances = ["------"]
    Measurement = "win_system"
    # Set to true to include _Total instance when querying for all (*).
    #IncludeTotal=false

  [[inputs.win_perf_counters.object]]
    # Example query where the Instance portion must be removed to get data back,
    # such as from the Memory object.
    ObjectName = "Memory"
    Counters = [
      "Available Bytes",
      "Cache Faults/sec",
      "Demand Zero Faults/sec",
      "Page Faults/sec",
      "Pages/sec",
      "Transition Faults/sec",
      "Pool Nonpaged Bytes",
      "Pool Paged Bytes",
      "Standby Cache Reserve Bytes",
      "Standby Cache Normal Priority Bytes",
      "Standby Cache Core Bytes",
      "% Committed Bytes In Use",
    ]
    # Use 6 x - to remove the Instance bit from the query.
    Instances = ["------"]
    Measurement = "win_mem"
    # Set to true to include _Total instance when querying for all (*).
    #IncludeTotal=false

  [[inputs.win_perf_counters.object]]
    # Example query where the Instance portion must be removed to get data back,
    # such as from the Paging File object.
    ObjectName = "Paging File"
    Counters = [
      "% Usage",
    ]
    Instances = ["_Total"]
    Measurement = "win_swap"


# Windows system plugins using WMI (disabled by default, using
# win_perf_counters over WMI is recommended)


# # Read metrics about cpu usage
# [[inputs.cpu]]
#   ## Whether to report per-cpu stats or not
#   percpu = true
#   ## Whether to report total system cpu stats or not
#   totalcpu = true
#   ## If true, collect raw CPU time metrics.
#   collect_cpu_time = false
#   ## If true, compute and report the sum of all non-idle CPU states.
#   report_active = false


# # Read metrics about disk usage by mount point
# [[inputs.disk]]
#   ## By default stats will be gathered for all mount points.
#   ## Set mount_points will restrict the stats to only the specified mount points.
#   # mount_points = ["/"]
#
#   ## Ignore mount points by filesystem type.
#   ignore_fs = ["tmpfs", "devtmpfs", "devfs", "overlay", "aufs", "squashfs"]


# # Read metrics about disk IO by device
# [[inputs.diskio]]
#   ## By default, telegraf will gather stats for all devices including
#   ## disk partitions.
#   ## Setting devices will restrict the stats to the specified devices.
#   # devices = ["sda", "sdb", "vd*"]
#   ## Uncomment the following line if you need disk serial numbers.
#   # skip_serial_number = false
#   #
#   ## On systems which support it, device metadata can be added in the form of
#   ## tags.
#   ## Currently only Linux is supported via udev properties. You can view
#   ## available properties for a device by running:
#   ## 'udevadm info -q property -n /dev/sda'
#   # device_tags = ["ID_FS_TYPE", "ID_FS_USAGE"]
#   #
#   ## Using the same metadata source as device_tags, you can also customize the
#   ## name of the device via templates.
#   ## The 'name_templates' parameter is a list of templates to try and apply to
#   ## the device. The template may contain variables in the form of '$PROPERTY' or
#   ## '${PROPERTY}'. The first template which does not contain any variables not
#   ## present for the device is used as the device name tag.
#   ## The typical use case is for LVM volumes, to get the VG/LV name instead of
#   ## the near-meaningless DM-0 name.
#   # name_templates = ["$ID_FS_LABEL","$DM_VG_NAME/$DM_LV_NAME"]


# # Read metrics about memory usage
# [[inputs.mem]]
#   # no configuration


# # Read metrics about swap memory usage
# [[inputs.swap]]
#   # no configuration


# Read metrics from Microsoft SQL Server
[[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, in particular, tls connections can be created like so:
  ##   "encrypt=true;certificate=<cert>;hostNameInCertificate=<SqlServer host fqdn>"
  servers = [
    "Server=xxxxx.database.windows.net;Port=1433;User Id=xxxxxxx;Password=xxxxxx;database=xxxxxx;app name=xxxxx;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 = "AzureSQLDB"

  ## Optional parameter, setting this to 2 will use a new version
  ## of the collection queries that break compatibility with the original dashboards.
  ## Version 2 - is compatible from SQL Server 2008 Sp3 and later versions and also for SQL Azure DB
  ## Version 2 is in the process of being deprecated, please consider using database_type.
  ## query_version = 2

  ## If you are using AzureDB, setting this to true will gather resource utilization metrics
  ## azuredb = true

  ## Possible queries accross different versions of the collectors
  ## Queries enabled by default for specific Database Type

  ## database_type =  AzureSQLDB  by default collects the following queries
  ## - AzureSQLDBWaitStats
  ## - AzureSQLDBResourceStats 
  ## - AzureSQLDBResourceGovernance
  ## - AzureSQLDBDatabaseIO
  ## - AzureSQLDBServerProperties
  ## - AzureSQLDBSQLOsWaitstats
  ## - AzureSQLDBMemoryClerks
  ## - AzureSQLDBPerformanceCounters
  ## - AzureSQLDBRequests
  ## - AzureSQLDBSchedulers

   ## database_type =  AzureSQLManagedInstance by default collects the following queries
   ## - AzureSQLMIResourceStats 
   ## - AzureSQLMIResourceGovernance 
   ## - AzureSQLMIDatabaseIO 
   ## - AzureSQLMIServerProperties 
   ## - AzureSQLMIOsWaitstats 
   ## - AzureSQLMIMemoryClerks
   ## - AzureSQLMIPerformanceCounters
   ## - AzureSQLMIDBRequests
   ## - AzureSQLMISchedulers

   ## database_type =  SQLServer by default collects the following queries
   ## - SQLServerPerformanceCounters 
   ## - SQLServerWaitStatsCategorized 
   ## - SQLServerDatabaseIO 
   ## - SQLServerProperties 
   ## - SQLServerMemoryClerks 
   ## - SQLServerSchedulers
   ## - SQLServerRequests
   ## - SQLServerVolumeSpace
   ## - SQLServerCpu

  ## Version 2 by default collects the following queries
  ## Version 2 is being deprecated, please consider using database_type.
  ## - PerformanceCounters
  ## - WaitStatsCategorized
  ## - DatabaseIO
  ## - ServerProperties
  ## - MemoryClerk
  ## - Schedulers
  ## - SqlRequests
  ## - VolumeSpace
  ## - Cpu

  ## Version 1 by default collects the following queries
  ## Version 1 is deprecated, please consider using database_type.
  ## - PerformanceCounters
  ## - WaitStatsCategorized
  ## - CPUHistory
  ## - DatabaseIO
  ## - DatabaseSize
  ## - DatabaseStats
  ## - DatabaseProperties
  ## - MemoryClerk
  ## - VolumeSpace
  ## - PerformanceMetrics



  ## A list of queries to include. If not specified, all the above listed queries are used.
  # include_query = []

  ## A list of queries to explicitly ignore.
  exclude_query = [ 'Schedulers' , 'SqlRequests' ]

System info:

Windows 2016. Telegraf 1.15.3

Steps to reproduce:

1. Running Telegraf with standard [[inputs.sqlserver]] configuration.
2. chose new database_type = AzureSQLDB config switch

Expected behavior:

The Configuration: section suggests the "database_type" has been included, therefore
Azure stats should be collected as per SQL Server Input Plugin default options.

Actual behavior:

Error on trying to start telegraf.

"field corresponding to `database_type' is not defined in sqlserver.SQLServer"

I'm assuming that the functionality has yet to be adopted? Thanks.

Additional info:

[johndnlightnit]

I built and tried denzilribeiro / telegraf forked from influxdata/telegraf, But this has the same issue. "field corresponding to `database_type' is not defined in sqlserver.SQLServer" Thanks.

[ssoroka]

can you share your whole config? It sounds like a TOML parsing error. database_type is definitely a field on the sqlserver input.

[johndnlightnit]

Hi Thanks for that, I'm sure its something simple, but try it in different places, and capitalisation etc.

I have updated my config in my original post. Hope that helps. Thanks

[Trovalo]

I've just built the master branch to replicate the issue but everything works fine to me.
here is my sqlserver config

[[inputs.sqlserver]]
  servers = [
    "Server=_______.database.windows.net;User Id=_______;Password=_______;app name=telegraf;log=1;",
  ]
  database_type = "AzureSQLDB"

[johndnlightnit]

Hi Giovanni

Can you send me the executable, so I cant test, so that its not the way I have compiled the code.

Very many thanks

John

From: Giovanni Luisotto [e-mail]
Sent: 24 September 2020 10:29
To: influxdata/telegraf [e-mail]
Cc: John Denny [e-mail]; Author [e-mail]
Subject: Re: [influxdata/telegraf] SQL Server input plug-in erorr when using "database_type" config switch in telegraf. (#8155)

I've just built the master branch to replicate the issue but everything works fine to me.
here is my sqlserver config

[[inputs.sqlserver]]

servers = [

"Server=_______.database.windows.net;User Id=_______;Password=_______;app name=telegraf;log=1;",

]

database_type = "AzureSQLDB"

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/telegraf/issues/8155#issuecomment-698230067, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7DKZB6T3HLFQR4VIADGL3SHMGPBANCNFSM4RTHFR3Q.

LEGAL DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for use by the individual or entity to whom they are addressed. If you have received this transmission in error please contact the sender or your system manager. Any views or opinions presented by the sender of this message are not necessarily those of nlightn-IT Ltd. The recipient should check this email and any attachments for the presence of viruses. nlightn-IT Ltd accepts no liability for any damage caused by any virus transmitted by this email. nlightn-IT Ltd, Registered in England No: 04317633 Registered Office: Elmton Lodge Farm, Spring Lane, Elmton, Worksop, S80 4LX

[Trovalo]

I've built it on windows, but that should be fine since you are gathering the win_perf_counters.

here you go:
https://drive.google.com/file/d/1v2s0zlJNmNGeeGQgvV032EwH28ZaUlM8/view?usp=sharing

[johndnlightnit]

Cheers, Ill test now.

John

From: Giovanni Luisotto [e-mail]
Sent: 24 September 2020 10:58
To: influxdata/telegraf [e-mail]
Cc: John Denny [e-mail]; Author [e-mail]
Subject: Re: [influxdata/telegraf] SQL Server input plug-in erorr when using "database_type" config switch in telegraf. (#8155)

I've built it on windows, but that should be fine since you are gathering the win_perf_counters.

here you go:
https://drive.google.com/file/d/1v2s0zlJNmNGeeGQgvV032EwH28ZaUlM8/view?usp=sharing

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/telegraf/issues/8155#issuecomment-698244502, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7DKZCP7UW2AKYW4GJEJ33SHMJ2RANCNFSM4RTHFR3Q.

LEGAL DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for use by the individual or entity to whom they are addressed. If you have received this transmission in error please contact the sender or your system manager. Any views or opinions presented by the sender of this message are not necessarily those of nlightn-IT Ltd. The recipient should check this email and any attachments for the presence of viruses. nlightn-IT Ltd accepts no liability for any damage caused by any virus transmitted by this email. nlightn-IT Ltd, Registered in England No: 04317633 Registered Office: Elmton Lodge Farm, Spring Lane, Elmton, Worksop, S80 4LX

[johndnlightnit]

[cid:[email protected]]
Ill try again and build it in Linux

Thanks for your help so far, but as far as you are aware, with the main master branch on Telegraf the databases_type should work.

Cheers

John

From: Giovanni Luisotto [e-mail]
Sent: 24 September 2020 10:58
To: influxdata/telegraf [e-mail]
Cc: John Denny [e-mail]; Author [e-mail]
Subject: Re: [influxdata/telegraf] SQL Server input plug-in erorr when using "database_type" config switch in telegraf. (#8155)

I've built it on windows, but that should be fine since you are gathering the win_perf_counters.

here you go:
https://drive.google.com/file/d/1v2s0zlJNmNGeeGQgvV032EwH28ZaUlM8/view?usp=sharing

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/telegraf/issues/8155#issuecomment-698244502, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7DKZCP7UW2AKYW4GJEJ33SHMJ2RANCNFSM4RTHFR3Q.

LEGAL DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for use by the individual or entity to whom they are addressed. If you have received this transmission in error please contact the sender or your system manager. Any views or opinions presented by the sender of this message are not necessarily those of nlightn-IT Ltd. The recipient should check this email and any attachments for the presence of viruses. nlightn-IT Ltd accepts no liability for any damage caused by any virus transmitted by this email. nlightn-IT Ltd, Registered in England No: 04317633 Registered Office: Elmton Lodge Farm, Spring Lane, Elmton, Worksop, S80 4LX

[Trovalo]

Have you tried to use the nightly builds of Telegraf? does the problem persist?
https://github.com/influxdata/telegraf#nightly-builds

[0x000flo]

Hello folks,
I can confirm this issue happens in telegraf-1.15.3_windows_amd64 and it is fixed in the nightly build (telegraf-nightly_windows_amd64\telegraf-1.16.0)

[johndnlightnit]

Cheers Ill test

John

From: 0x000flo [e-mail]
Sent: 01 October 2020 16:52
To: influxdata/telegraf [e-mail]
Cc: John Denny [e-mail]; Author [e-mail]
Subject: Re: [influxdata/telegraf] SQL Server input plug-in erorr when using "database_type" config switch in telegraf. (#8155)

Hello folks,
I can confirm this issue happens in telegraf-1.15.3_windows_amd64 and it is fixed in the nightly build (telegraf-nightly_windows_amd64\telegraf-1.16.0)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/telegraf/issues/8155#issuecomment-702229208, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7DKZBAWYWOCXKAK3BLO6LSISQRXANCNFSM4RTHFR3Q.

LEGAL DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for use by the individual or entity to whom they are addressed. If you have received this transmission in error please contact the sender or your system manager. Any views or opinions presented by the sender of this message are not necessarily those of nlightn-IT Ltd. The recipient should check this email and any attachments for the presence of viruses. nlightn-IT Ltd accepts no liability for any damage caused by any virus transmitted by this email. nlightn-IT Ltd, Registered in England No: 04317633 Registered Office: Elmton Lodge Farm, Spring Lane, Elmton, Worksop, S80 4LX

[Trovalo]

Ok, I think I've got this, I just reread the whole conversation and I think it's just a big misunderstanding.

I just had a look at the source code in the v1.15.3, and the parameter database_type does not exist.
If you are looking at the docs on Github, well that displays the latest changes, which you can have by making a build yourself or by using the nightly releases (which are just builds of the master branch).
The master branch of Telegraf does NOT contain the latest release, it contains changes that are good to go, but that does not mean that those features are going to be released soon.

If the rules have not changed, big changes have to wait for major releases, minor releases just address bug fixes and small tweaks.

The _database_type_ parameter won't be officially released until the next major release, the 1.16.0 milestone exists but does not have a due date (the due date is was usually added 1-2 weeks before the release tho).

As of now, the best you with the official release (v1.15.3) is using the query_version = 2 parameter.

There are still changes pending on the SqlServer plugin you are seeing now on the master branch, and some PRs waiting to be merged in order to fix minor issues we have discovered.

You can use the nightly builds (master branch) at your own risk to get early access to new features without having to wait for the next major release. We (contributors) do our best to ensure that the changes we made are actually working but as you know bugs happen...
I personally encourage you to report any issue you find while using the nightly builds, so it can be fixed.

TLDR

• The master branch of Telegraf does NOT contain the latest release, it contains changes that are good to go
• The nightly builds (builds of the master branch) allow you to use what you see in the master branch
• The database_type parameter won't be officially released until the next major release (no due date yet)
• The best you can with v1.15.3 is using the query_version = 2 parameter

[johndnlightnit]

Thanks for the information, I did wonder if this was the case, and this makes perfect sense. Thanks for taking the time to explain it to me.

From: Giovanni Luisotto [e-mail]
Sent: 01 October 2020 20:05
To: influxdata/telegraf [e-mail]
Cc: John Denny [e-mail]; Author [e-mail]
Subject: Re: [influxdata/telegraf] SQL Server input plug-in erorr when using "database_type" config switch in telegraf. (#8155)

Ok, I think I've got this, I just reread the whole conversation and I think it's just a big misunderstanding.

I just had a look at the source code in the v1.15.3, and the parameter database_type does not exist.
If you are looking at the docs on Github, well that displays the latest changes, which you can have by making a build yourself or by using the nightly releases (which are just builds of the master branch).
The master branch of Telegraf does NOT contain the latest release, it contains changes that are good to go, but that does not mean that those features are going to be released soon.

If the rules have not changed, big changes have to wait for major releases, minor releases just address bug fixes and small tweaks.

The database_type parameter won't be officially released until the next major release, the 1.16.0 milestone exists but does not have a due date (the due date is was usually added 1-2 weeks before the release tho).

As of now, the best you with the official release (v1.15.3) is using the query_version = 2 parameter.

There are still changes pending on the SqlServer plugin you are seeing now on the master branch, and some PRs waiting to be merged in order to fix minor issues we have discovered.

You can use the nightly builds (master branch) at your own risk to get early access to new features without having to wait for the next major release. We (contributors) do our best to ensure that the changes we made are actually working but as you know bugs happen...
I personally encourage you to report any issue you find while using the nightly builds, so it can be fixed.

TLDR

• The master branch of Telegraf does NOT contain the latest release, it contains changes that are good to go
• The nightly builds (builds of the master branch) allow you to use what you see in the master branch
• The database_type parameter won't be officially released until the next major release (no due date yet)
• The best you can with v1.15.3 is using the query_version = 2 parameter

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/influxdata/telegraf/issues/8155#issuecomment-702337880, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7DKZAKNTLVOO3W5QC4ZLLSITHFLANCNFSM4RTHFR3Q.

LEGAL DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for use by the individual or entity to whom they are addressed. If you have received this transmission in error please contact the sender or your system manager. Any views or opinions presented by the sender of this message are not necessarily those of nlightn-IT Ltd. The recipient should check this email and any attachments for the presence of viruses. nlightn-IT Ltd accepts no liability for any damage caused by any virus transmitted by this email. nlightn-IT Ltd, Registered in England No: 04317633 Registered Office: Elmton Lodge Farm, Spring Lane, Elmton, Worksop, S80 4LX

[Trovalo]

@johndnlightnit if you don't have any other doubt the issue can be close