3 ms·

In your example I'd probably have the direction in the measurement name. e.g. { "name": "network_bytesin", "tags": {"host" "example.com"}, "fields": {"va

by pauldix 11y ago

In your example I'd probably have the direction in the measurement name. e.g. { "name": "network_bytesin", "tags": {"host" "example.com"}, "fields": {"value": 50} } For fields, you generally only want to put two pieces of data together in a single point (thus in two fields) if you're always going to be querying them together. Either by pulling the values out, or filtering on a WHERE clause. Unrelated to this, we've created a line protocol to write data in and it's a much more compact way to show a point: network_bytesin,host=example.com value=50 Details here: https://github.com/influxdb/influxdb/pull/2696 https://github.com/influxdb/influxdb/pull/2696

victorhooi 11y ago
Aha, fair enough - so if you only sometimes query the values together, you should separate them out into discrete series =). For a logline, the sort of metrics we'd get would be things like query duration, database, client ID etc. You've often query them together, but you'd also query them separately, so I guess that also makes sense as multiple separate series. Interesting, that line protocol looks cool and seems like it'd be more efficient on the wire. Will the drivers (e.g. Python, Go) be updated to take advantage of this new endpoint? Finally, I see there's also a ticket open for binary protocols: https://github.com/influxdb/influxdb/issues/139 https://github.com/influxdb/influxdb/issues/139 Do you see that as being still potentially useful?
- pauldix 11y ago
  The Go client has already been updated. We'll be updating the Ruby and front end JS client. Hopefully the community will jump on updating the other clients once we release 0.9.0. It's a super simple protocol so I don't imagine it'll take much work. The binary protocol is probably much less useful now. HTTP + GZip of the line protocol will already saturate what our storage engine can do at this point. In fact, I'm going to close that out right now...

by pauldix 11y ago

victorhooi 11y ago

Aha, fair enough - so if you only sometimes query the values together, you should separate them out into discrete series =). For a logline, the sort of metrics we'd get would be things like query duration, database, client ID etc. You've often query them together, but you'd also query them separately, so I guess that also makes sense as multiple separate series. Interesting, that line protocol looks cool and seems like it'd be more efficient on the wire. Will the drivers (e.g. Python, Go) be updated to take advantage of this new endpoint? Finally, I see there's also a ticket open for binary protocols: https://github.com/influxdb/influxdb/issues/139 https://github.com/influxdb/influxdb/issues/139 Do you see that as being still potentially useful?

pauldix 11y ago
The Go client has already been updated. We'll be updating the Ruby and front end JS client. Hopefully the community will jump on updating the other clients once we release 0.9.0. It's a super simple protocol so I don't imagine it'll take much work. The binary protocol is probably much less useful now. HTTP + GZip of the line protocol will already saturate what our storage engine can do at this point. In fact, I'm going to close that out right now...