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
Can the target allocator apply the relabel configs prior to allocation so we can drop any unnecessary targets? This would also help reduce load on the collectors and ensure that the allocation is more evenly distributed.
For example in the test setup I have, the /metrics endpoint says the TA is allocating 36 targets, but only 3 of those targets are actually valid based on the relabel configs I set.
The text was updated successfully, but these errors were encountered:
Hey Kelsey! Thank you for submitting this issue, definitely something I've been thinking about too. My team can take a look at implementing this behavior. Not sure when we'll get to it, we may have some time in the coming weeks.
Can the target allocator apply the relabel configs prior to allocation so we can drop any unnecessary targets? This would also help reduce load on the collectors and ensure that the allocation is more evenly distributed.
For example in the test setup I have, the
/metrics
endpoint says the TA is allocating 36 targets, but only 3 of those targets are actually valid based on the relabel configs I set.The text was updated successfully, but these errors were encountered: