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
Let's start by telling that this is might be a breaking change for this measurement, I'm considering only the v2 of the measurement "sqlserver_database_io".
The main purpose of this measurement is to get IO info like the "Disk Latency", which is the most important to me.
Those data come from the dynamic management view in SQL Server sys.dm_io_virtual_file_stats. The view outputs incremental counters which restart from zero when the instance is restarted.
The counters are initialized to empty whenever the SQL Server (MSSQLSERVER) service is started.
The query is compatible with the on-premise version of SQL Server starting from SQL Server 2008.
The same/similar logic can be applied also to "Azure SQL DB", without "by disk" metrics since that info is not available. (I don't have an Azure SQL DB so I might be wrong)
The updated measurement will have the following structure: Tags
sql_instance
database_name
physical_filename
logical_filename
file_type (which is kept as-is: possible values are "ROWS"|"LOG"|"FILESTREAM"|"FULLTEXT")
volume_mount_point (which usually is the disk volume itself but can also be a subpath)
Fields
read_latency_ms (this is the actual istantaneous latency)
write_latency_ms (this is the actual istantaneous latency)
overall_latency_ms (this is the actual istantaneous latency)
avg_bytes_per_read
avg_bytes_per_write
avg_bytes_per_transfer
The query also adds the overall disk stats, regardless of the single database, for these rows tags like "database_name" and "physical_filename" have "All Databases" and "All Files" as value
Note that the current query fields are not included, but can be included to maintain retro compatibility. (although some renaming is necessary for the "latency" fields)
Feature Request
Let's start by telling that this is might be a breaking change for this measurement, I'm considering only the v2 of the measurement "sqlserver_database_io".
The main purpose of this measurement is to get IO info like the "Disk Latency", which is the most important to me.
Those data come from the dynamic management view in SQL Server sys.dm_io_virtual_file_stats. The view outputs incremental counters which restart from zero when the instance is restarted.
Proposal:
Change the query to get the data to the attachment Disk latency for telegraf.txt
The updated measurement will have the following structure:
Tags
Fields
The query also adds the overall disk stats, regardless of the single database, for these rows tags like "database_name" and "physical_filename" have "All Databases" and "All Files" as value
Note that the current query fields are not included, but can be included to maintain retro compatibility. (although some renaming is necessary for the "latency" fields)
My query comes from those references:
Current behavior:
As of now, the measurement contains the following data, which are the fields outputted by the view as-is:
Tags
Fields
Here is the link to the query that extracts those data
telegraf/plugins/inputs/sqlserver/sqlserver.go
Line 353 in e9e4f2c
Desired behavior:
The measurement contains:
Use case:
The text was updated successfully, but these errors were encountered: