Skip to content

Conversation

@SungJin1212
Copy link
Member

Followed up #7155, clean up cortex_distributor_ingester_push_timeouts_total for inactive user.

Which issue(s) this PR fixes:
Fixes #

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

d.incomingMetadata.DeleteLabelValues(userID)
d.nonHASamples.DeleteLabelValues(userID)
d.latestSeenSampleTimestampPerUser.DeleteLabelValues(userID)
d.distributorIngesterPushTimeoutPerUser.DeleteLabelValues(userID)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this metric needs to be per user?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When there is a push timeout, usually it is not because of data ingested from a specific user, it is more like a problem between ingester and distributor fleet. Then basically all users in the cluster will be impacted. I don't see much a value here to make this metric per tenant

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes sense, I deleted userID label in this PR.

Signed-off-by: SungJin1212 <tjdwls1201@gmail.com>
@SungJin1212 SungJin1212 force-pushed the clean-up-cortex_distributor_ingester_push_timeouts_total branch from 79f3e4f to 6c95e88 Compare January 22, 2026 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants