You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently migrated from tempo single-binary to tempo-distributed with S3 as the backend object storage. We are using tempo 2.1.1. With tempo-distributed, we started noticing a weird issue where label names disappear in the dropdowns after about an hour. While the labels do show up if traces are continuously being sent, when the traces stop coming in, the labels disappear after an hour. I can run searches and the traces do show up (meaning tempo has not lost data) but the labels still stay unpopulated. Please see screenshot below.
I looked through the query frontend logs and it shows 200 success calls for /api/search/tag but seems no data is returned.
I came across this issue grafana/tempo#2565 which seems to be related to the problem I am facing but I am not entirely sure. Any advice and guidance will be really great on how to solve this. I have provided the tempo config values below. Is there a config that I somehow missed which might be the culprit?
We recently migrated from tempo single-binary to tempo-distributed with S3 as the backend object storage. We are using tempo 2.1.1. With tempo-distributed, we started noticing a weird issue where label names disappear in the dropdowns after about an hour. While the labels do show up if traces are continuously being sent, when the traces stop coming in, the labels disappear after an hour. I can run searches and the traces do show up (meaning tempo has not lost data) but the labels still stay unpopulated. Please see screenshot below.
I looked through the query frontend logs and it shows 200 success calls for /api/search/tag but seems no data is returned.
I came across this issue grafana/tempo#2565 which seems to be related to the problem I am facing but I am not entirely sure. Any advice and guidance will be really great on how to solve this. I have provided the tempo config values below. Is there a config that I somehow missed which might be the culprit?
The text was updated successfully, but these errors were encountered: