influx2otel: Improve handling of unknown metric type
jacobmarble opened this issue · 1 comments
jacobmarble commented
Reported by @codeboten influxdata/telegraf#9228 (comment)
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
2021-05-12T21:12:35Z W! [outputs.opentelemetry] failed to add point: gauge field not found
The gauge logic anticipates field gauge exists, but it does not. It looks like the fallback metric type logic was triggered, which means the line was interpreted as a gauge, but the schema requirements are too strict to do anything useful with the data.
In the fallback case, if exactly one field exists, then it should be used as the gauge value.
jacobmarble commented
Fixed in 56c5b37