Chronograf: RFC: How to handle warning: 'unsupported mean iterator type: *influxql.stringInterruptIterator'

[jaredscheib]

It looks like at least one (if not more) field types can't have mean (if not other functions) applied to them. For example, as seen below, when applying mean to uptime_format, which is included in telegraf.autogen, a warning is returned. This actually results in no data for any queries being returned, which is a jarring UX.

I suppose we should disallow this function from being applied to this field? Or is there some larger set of functions we should know about that can't be applied to certain fields? Maybe this could be supplied as metadata by InfluxDB or by Chronograf server and we could programmatically bar certain functions from being applied to certain fields?

[121watts]

@danielnelson thoughts?

[danielnelson]

This field is a string which is why you can't perform the mean operation on it.

[russorat]

@alexpaxton think there is a way for us to figure out the type of the fields and choose a different default function for string fields? like count?

[alexpaxton]

@russorat I can investigate -- this could be rolled into an updated design for the function selector

[russorat]

closing due to inactivity

[pisti2010]

Will this not be fixed at all?

[halfa]

This likely happens because you stored strings instead of numbers in influxdb. Try to format your input with proper numbers instead.