Closed luthes closed 10 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
@luthes hey! Thanks for opening the issue, I was able to reproduce using your config. Your intuition was right, there is a typing issue with the rows.Scan()
(from database/sql
) used in client.go
.
Component(s)
receiver/snowflake
What happened?
Description
When using the Snowflake receiver, I noticed that we weren't getting the storage metrics I'd expect:
snowflake.storage.stage_bytes.total
,snowflake.storage.storage_bytes.total
orsnowflake.storage.failsafe_bytes.total
. It does appear that the query for this is running, as I can see the query in the query history. I don't, however, see this getting sent to my OTLP endpoint (New Relic, in this case), or even logged out using the debug exporter.All other metrics are received, including optional metrics.
Steps to Reproduce
Docker container with config for Snowflake connector and
Expected Result
I should see logs in the debug exporter that it's finding metrics that it's querying data, or at least
Actual Result
No logs, no errors, no data in otlp endpoint.
Collector version
0.90.1
Environment information
Official Docker Container
OpenTelemetry Collector configuration
Log output
Additional context
I'm not sure if it matters, but the type in the client.go is of type int64, but it looks like the type returned from Snowflake might be of type float64 like some of the other types.
For example, this query (from the client.go):
returns the following:
But frankly, I'm not sure if there is some type conversion happening somewhere that would impact this, or if it matters at all.
Just to be clear, these are the only three metrics that don't work. If I explicity enable all other metrics, or allow defaults with empty
metric:
, I see all of the other data points reflected in the OTLP endpoint.