Thanks for the quick answer and the clarification! *>In general more tags per measurement and fewer measurements overall is preferred to more measurements with fewer tags each. I would recommend having log and protocol as tags on a single measurement.*
Great, that's what i assumed as well. So we use one measurement name per protocol (as they might require different sensors) and just tag each series with a uid. *>Series belong to measurements in InfluxDB jargon, not the other way around. ...* I got i bit confused with the terminology, as in the query results what i assumed to be measurements, are returned as part of the series key https://docs.influxdata.com/influxdb/v1.0/guides/querying_data/ But now that you spelled it out its clear to me as well: A series is always a part of the measurement, but never the other way around. So queries return series and not measurements, as this is the only way to have a consistently named field, if one may query for a subset of a measurement. Am Freitag, 16. September 2016 17:24:45 UTC+2 schrieb Sean Beckett: > > > Is it better to store the whole set in one series(measurement) and add > tags to them so they can be filtered later, or store each measurement in > its own series and simply add a tag that defines the protocol? > > Series belong to measurements in InfluxDB jargon, not the other way > around. Rewording this to be consistent with terminology (I think): > > > Is it better to store every series in one measurement using tags, or > store each set of metrics in its own measurement and simply add a tag that > defines the protocol? > > In general more tags per measurement and fewer measurements overall is > preferred to more measurements with fewer tags each. I would recommend > having log and protocol as tags on a single measurement. > > > > On Fri, Sep 16, 2016 at 8:42 AM, Felix Horvat <[email protected] > <javascript:>> wrote: > >> Sorry for the generic title, i didn't manage to find a descriptive name. >> We have logs with sensor data we want to push to influx db. Each of these >> logs is acquired using a specific protocol. This defines how the data is do >> be acquired, thus what has to be done while the data is being acquired. >> So we end up with sets of logs where each set contains data for a >> specific "protocol". >> Each log might contain more then 1 million datapoints. The timestamps of >> these logs might overlap, so that for a given time interval there might be >> more then one valid log. Also we might have thousands of logs. >> >> The question is now: What structure is best practice for storing this >> kind of data in influxdb? >> Is it better to store the whole set in one series(measurement) and add >> tags to them so they can be filtered later, or store each measurement in >> its own series and simply add a tag that defines the protocol? >> >> >> -- >> Remember to include the InfluxDB version number with all issue reports >> --- >> You received this message because you are subscribed to the Google Groups >> "InfluxDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/influxdb. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/influxdb/690a5ab6-8754-4561-9126-b0773510f0cb%40googlegroups.com >> >> <https://groups.google.com/d/msgid/influxdb/690a5ab6-8754-4561-9126-b0773510f0cb%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Sean Beckett > Director of Support and Professional Services > InfluxDB > -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/c2f1d799-11ae-40b0-902d-80fb1022c12d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
