mysql receiver sql parse error: Scan er ror on column index 6, name \"SUM_TIMER_DELETE/1000\": converting driver.Value type []uint8 (\"0.0000\") to a int64: invalid syntax

[devilcoolyue]

Component(s)

receiver/mysql

What happened?

2025-03-07T17:25:13.135+0800 error mysqlreceiver@v0.121.0/scraper.go:443 Failed to fetch table io_waits stats {"otelcol.component.id": "mysql/mysqlv_1897931734926893056", "otelcol.component.kind": "Receiver", "otelcol.signal": "metrics", "error": "sql: Scan er
ror on column index 6, name "SUM_TIMER_DELETE/1000": converting driver.Value type []uint8 ("0.0000") to a int64: invalid syntax"}
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver.(*mySQLScraper).scrapeTableIoWaitsStats
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver@v0.121.0/scraper.go:443
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver.(*mySQLScraper).scrape
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver@v0.121.0/scraper.go:90
go.opentelemetry.io/collector/scraper.ScrapeMetricsFunc.ScrapeMetrics
go.opentelemetry.io/collector/scraper@v0.121.0/metrics.go:24
this commit cause this bug :ad60f51

Collector version

v0.121.0

Environment information

No response

OpenTelemetry Collector configuration

Log output

2025-03-07T17:25:13.135+0800    error   mysqlreceiver@v0.121.0/scraper.go:443   Failed to fetch table io_waits stats    {"otelcol.component.id": "mysql/mysqlv_1897931734926893056", "otelcol.component.kind": "Receiver", "otelcol.signal": "metrics", "error": "sql: Scan er
ror on column index 6, name \"SUM_TIMER_DELETE/1000\": converting driver.Value type []uint8 (\"0.0000\") to a int64: invalid syntax"}                                                                                                                                         
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver.(*mySQLScraper).scrapeTableIoWaitsStats                                                                                                                                                      
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver@v0.121.0/scraper.go:443                                                                                                                                                              
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver.(*mySQLScraper).scrape                                                                                                                                                                       
        github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver@v0.121.0/scraper.go:90                                                                                                                                                               
go.opentelemetry.io/collector/scraper.ScrapeMetricsFunc.ScrapeMetrics                                                                                                                                                                                                         
        go.opentelemetry.io/collector/scraper@v0.121.0/metrics.go:24

Additional context

No response

[devilcoolyue]

cc @atoulme I think all SQL expressions with division by 1000 (like SUM_TIMER_DELETE/1000) should be wrapped with either FLOOR or ROUND functions to ensure they return proper integer values instead of floating-point numbers.

[atoulme]

Duplicate for #38276. Please offer a PR to fix the issue - and we're looking for a codeowner, if you're interested.