@Anaisdg Thank you for the reply. The behavior actually changed a little after updating to influx 1.7.9:
Now the query works as long as I only query data after the incident. As soon as I start a query that includes data from before the accident only the old data can be read. I pinpointed the actual time it happened and this is the data directly around the incident:
> SELECT * FROM "temperature" WHERE time > 1572036412756096000 and time < 1572037373055757000
name: temperature
time location location_1 value
---- -------- ---------- -----
1572036532738133000 living 22.6
1572036553715978000 outdoor 11.7
1572036581190571000 work 22.7
1572036641196348000 work 22.6
1572036643036868000 bed 19.7
1572036703094991000 bed 19.9
1572036763123191000 bed 19.8
1572036821191581000 work 22.7
1572037003275377000 bed 19.9
1572037061201475000 work 22.6
1572037063093457000 bed 19.8
1572037181203827000 work 22.7
1572037182982241000 bed 19.8
1572037192747410000 living 22.6
1572037213934115000 outdoor 11.8
1572037241180611000 work 22.7
1572037243092490000 bed 19.9
1572037252952408000 living 22.6
1572037273970923000 outdoor 11.8
1572037312771283000 living 22.6
1572037333805383000 outdoor 11.8
So as soon as a query for “location” contains data from both periods the data stored in “location_1” is not returned anymore. When querying only before or after this timeframe everything now (after the update) works as expected. I would still like to fix this though if somehow possible because grafana is not able to display long time queries correct anymore.
