Issue: Chart in tag browser not showing
# umh-supportt
trentc
11/04/2024, 5:48 PMIssue: Chart in tag browser not showing correct values?
trentc
11/04/2024, 5:49 PMWhy does the value jump from 1000 to 2500 almost immediately? This is not what it actually does....or what it shows in the historian.
trentc
11/04/2024, 5:50 PMj
Jermuk
11/04/2024, 7:22 PM@ricci2511
Jermuk
11/04/2024, 7:24 PMmaybe what could happen if there was a internet disconnection or something? the tag browser will show the values based on when they appeared in the dashboard, and not when the timestamp it said it was sent
l
Linear
11/04/2024, 7:25 PMt
trentc
11/04/2024, 9:07 PMThe historian, mqtt broker, and dashboard are all on the same instance in the cloud....if it shows in the historian, it went from mqtt to kafka to postgresql......assuming the tag browser in the console is sourcing it's data from kafka....there is no point of failure that is different than that of the historian....
trentc
11/04/2024, 9:08 PMwhat would cause missing data in the tag browser, but not in the historian....not only that....but why would the timestamps be off? if we just missed data for say 5 minutes....wouldn't there be a gap of data? instead of a jump in value at the next timestamp?
trentc
11/04/2024, 9:09 PMfor my data, the timestamp is being created by the processors that are default in umh.....there are no timestamps included in my payloads, or in the processor code.
trentc
11/04/2024, 9:11 PMBut again...it makes it all the way through the default processors to postgres with a good timestamp....
j
Jermuk
11/05/2024, 8:06 AMBecause it does not show historian data, it shows data in Kafka. So that you can also see data that is not stored in the time series data . As there could be data points without a timestamp, we take the timestamp “on arrival”. So when a lot of values arrive at the same time, it feels like a jump.
Does that make sense?
t
trentc
11/05/2024, 10:16 AMI guess that makes sense… I still don’t understand how it gets all the values timestamped properly in the pipeline… but not in the tag browser, unless the tag browser can’t keep up… or stops “listening “ for the data for some period.