Skip to content

Conversation

@olix0r
Copy link
Member

@olix0r olix0r commented Oct 12, 2025

The destination control's ip_port_subscriber and ip_port_updates metrics are potentailly exposed for every IP that is discovered. This is high cardinality and puts undo pressure on the metrics infrastructure.

This change drops these labels, so that there is a single ip_port_subscriber and ip_port_updates timeseries.

The destination control's ip_port_subscriber and ip_port_updates metrics are
potentailly exposed for every IP that is discovered. This is high cardinality
and puts undo pressure on the metrics infrastructure.

This change drops these labels, so that there is a single ip_port_subscriber and
ip_port_updates timeseries.
@olix0r olix0r marked this pull request as ready for review October 12, 2025 21:32
@olix0r olix0r requested a review from a team as a code owner October 12, 2025 21:32
@olix0r olix0r changed the title fix(destination): drop ip and port metric labels fix(destination)!: drop ip and port metric labels Oct 13, 2025
Copy link
Member

@adleong adleong left a comment

Choose a reason for hiding this comment

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

since we're changing the labels anyway, should we also change the metric name? "ip_port" probably doesn't make sense without ip and port labels.

@olix0r olix0r changed the title fix(destination)!: drop ip and port metric labels fix(destination)!: replace ip_port_subscribers with workload_subscribers Oct 13, 2025
@olix0r olix0r merged commit 3e89f44 into main Oct 13, 2025
67 of 69 checks passed
@olix0r olix0r deleted the ver/cardinal branch October 13, 2025 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants