@jackzampolin This is the follow up question from the webinar 30/3/2017 Optimizing TICK Stack
The question was if there are plans to"fix" the problem with storing two point with the same time stamp either by
- Adding another dimension in the time stamp field, eg 1490893591.1 and 1490893591.2 … 1490893591.n
- Or instead of merging, aggregating the fields eg 120, 130 ~ 125 using a mean or median or whatever makes sense
- any other solution?
This happens with our servers where we have around 50 concurrent requests per server which generate per request 1 point in influx. We use the random ns workaround to distinguish possible collisions since using the unique tag workaround might create a serie cardinality issue.
Does btw telegraf handle this problem when ingesting haproxy logs which have a ms accuracy and a lot of requests happen the same ms?