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
{{ message }}
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.
Consider:
A metric that is stale and thus doesn't live in MT's memory index but still lives in the regular table if it haven't been archived yet).
A delete query won't catch it. Normally this is fine. the metric won't be in the memory index and thus it can't be queried for data. If new data comes in, it will become un-stale and resurface its data. But that's the same behavior as the normal delete case of non-stale metrics, which also resurface if new data comes in.
Where this gets interesting though:
if you increase the max-stale time window, the metrics may resurface by themselves
revive functionality, as proposed in Ability to "revive" archived series #1976 may also mistakenly reintroduce metrics that may needed to be deleted. (as delete queries can't reach into the archive table)
The text was updated successfully, but these errors were encountered:
Dieterbe
changed the title
deletes don't affect stale metrics. They may resurface when max-stale gets increased
deletes don't affect stale metrics. They may resurface if max-stale gets increased
May 20, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Consider:
A metric that is stale and thus doesn't live in MT's memory index but still lives in the regular table if it haven't been archived yet).
A delete query won't catch it. Normally this is fine. the metric won't be in the memory index and thus it can't be queried for data. If new data comes in, it will become un-stale and resurface its data. But that's the same behavior as the normal delete case of non-stale metrics, which also resurface if new data comes in.
Where this gets interesting though:
The text was updated successfully, but these errors were encountered: