A few days ago one of my sensors sent completely wrong data which caused my statistics to be completely wrong. I looked for a way to remove the wrong data and since dropping doesn’t work when filtering by values I found a workaround that suggested inserting the whole table into a new one, dropping t…

It does sound similar to my problem but also is not solved so unfortunately it’s not helping me in any way.

@Qetesh whoops! I thought it was solved. Why can’t you read from the database even with the name change? Can you please provide an example of a query that isn’t working?

@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…

Hi @Qetesh , if I understand correctly you want to continue to use the tag value location not location_1, but the values for a certain time range are logged as location_1 and new values are being written with the correct tag location ? You should be able to fix this by reading all measurement points…

Hey @JeremySTX , it is a bit more confusing… both the old and the new values have the tag “location” - only when I do a query on a time range that includes data from before and after the incident the new values are marked as “location_1”. When I for example just select the last 10 minutes, I get co…

@Qetesh , I’m having trouble getting help to help you. In the meantime, could you please create an issue and share the link here? Perhaps @rawkode , has some solutions for you? Thank you. I’m sorry this is happening, and I hope I can give you a concrete solution soon. Right now the only suggestion …

UPDATE: I got the following advice from support, typically they do: -A select into – for the entire measurement. -You articulate all the fields and then you group by all the tags (less the one you are trying to get rid of) -Then you drop the measurement -Then you re-run the select into and move…

Hi @Anaisdg sorry for the late reply… A select into was what caused the problem at first so I am a bit reluctant here… Also you say to group by the tags less the one I want to get rid off - how do I do that if it has the same name? I don’t want to lose data… Sorry if my questions might seem stupid…

@Qetesh , No problem, I haven’t dealt with this problem personally either, so we’re both new to this. That direction was passed on to me by coworkers. So you can’t do a select * or a group by * because you’re trying to get rid of a tag. So you you need to select each field into a target measurement.…

Suddenly a duplicated _1 tag - apparently I messed up my database

Telegraf

Anaisdg November 1, 2019, 6:57pm 2

Hello @Qetesh,

Thanks for your question. This problem sounds similar to this post. Is there a fix in there for you?

Topic		Replies	Views
Why is my tag get duplicated suddenly and I can't select using the tag Telegraf influxdb , schema , influxql , query	11	2854	February 18, 2021
Timestamps accidentally inserted as tags influxdb , schema , performance	2	397	July 13, 2023
Restoring backup to existing database fail to search collectd , grafana , backup , query	4	700	August 31, 2020
Migration between databases and lost tags values	3	202	November 29, 2023
Overwrite data in InfluxDB InfluxDB 2 influxdb , telegraf , grafana	2	3880	November 16, 2021

Suddenly a duplicated _1 tag - apparently I messed up my database

Related topics