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
InfluxDB's plaintext Graphite input relies on fields being space-delimited in each entry. However, Carbon (for better or worse) is more forgiving (https://github.com/graphite-project/carbon/blob/master/lib/carbon/protocols.py#L74) when receiving plaintext metrics. Due to the behavior of Python 2.7's split method, it will accept tabs or an arbitrary number of spaces between fields as delimiters.
This ambiguity means that different producers of Graphite metrics (like Sensu metrics plugins) have different delimiters between fields and are therefore not compatible with InfluxDB as a Graphite receiver. What would be the implications of making the InfluxDB Graphite input (https://github.com/influxdb/influxdb/blob/master/src/api/graphite/graphite_metric.go#L31) compatible with these producers?
The text was updated successfully, but these errors were encountered:
InfluxDB's plaintext Graphite input relies on fields being space-delimited in each entry. However, Carbon (for better or worse) is more forgiving (https://github.com/graphite-project/carbon/blob/master/lib/carbon/protocols.py#L74) when receiving plaintext metrics. Due to the behavior of Python 2.7's split method, it will accept tabs or an arbitrary number of spaces between fields as delimiters.
This ambiguity means that different producers of Graphite metrics (like Sensu metrics plugins) have different delimiters between fields and are therefore not compatible with InfluxDB as a Graphite receiver. What would be the implications of making the InfluxDB Graphite input (https://github.com/influxdb/influxdb/blob/master/src/api/graphite/graphite_metric.go#L31) compatible with these producers?
The text was updated successfully, but these errors were encountered: