简体繁体 English

黎曼到InfluxDB事件下降

[英]Riemann to InfluxDB event drop

原文 2015-12-14 05:14:22 2 1 events/ timestamp/ logstash/ influxdb/ riemann

I have a simple setup which uses filebeat and topbeat to forward data to Logstash, which further forwards it to Riemann, which in turn sends it to InfluxDB 0.9. 我有一个简单的设置，它使用filebeat和topbeat将数据转发到Logstash，再将其转发到Riemann，后者再将其发送到InfluxDB 0.9。 I use Logstash to split an event into multiple events, all of which show up on Riemann logs (with the same timestamp). 我使用Logstash将一个事件拆分为多个事件，所有这些事件均显示在Riemann日志中（具有相同的时间戳）。 However, only one of these split events reaches my InfluxDB. 但是，这些拆分事件中只有一个到达我的InfluxDB。 Any help please? 有什么帮助吗？

1 个解决方案

In InfluxDB 0.9, a point is uniquely identified by the measurement name, full tag set, and the timestamp. 在InfluxDB 0.9中，一个点由测量名称，完整标签集和时间戳唯一标识。 If another point arrives later with identical measurement name, tag set, and timestamp, it will silently overwrite the previous point. 如果稍后到达的另一个点具有相同的测量名称，标记集和时间戳，则它将静默覆盖先前的点。 This is intentional behavior. 这是故意行为。

Since your timestamps are identical and you're writing to the same measurement, you must ensure that your tag set differs for each point you want to record. 由于您的时间戳是相同的，并且您要写入相同的度量，因此必须确保您要记录的每个点的标记集都不同。 Even something like fuzz=[1,2,3,4,5] will work to differentiate the points. 甚至像fuzz=[1,2,3,4,5]类的东西也可以用来区分这些点。