Mixin: Add alloy cluster label filters to dashboards

[gaantunes]

PR Description

This is including the new cluster_name label introduced here to all dashboards.

Which issue(s) this PR fixes

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[gaantunes]

@wildum WDYT about this? I have noticed you have only included this label to the alloy_config_hash, but I think we could gain from having it included in every metric when this config option is set, not only on the k8s world but everywhere.

[wildum]

all this branching is not scaling very well. If we add another variable it will just look awful. Isn't there a way to make this simpler? I'm not familiar with the dashboards config

[gaantunes]

Will consult @v-zhuravlev on this, since he is a jsonnet sorcerer.

[gaantunes]

@wildum any comments regarding the including of cluster_name label to all metrics? This PR assumes that is the case.

[thampiotr]

Could we instead recommend that if users have two or more Alloy clusters, then it's important to make them have a different job label value, so they can be distinguished easily?

I think that would be cleaner then having an ever-increasing list of labels to group by.

[gaantunes]

Could we instead recommend that if users have two or more Alloy clusters, then it's important to make them have a different job label value, so they can be distinguished easily?

I think that would be cleaner then having an ever-increasing list of labels to group by.

There is currently no way to support it on integrations, unfortunately. The standard we apply for all integrations is a static job label and a platform specific cluster label that is spread to all metrics.

We currently use this static job label to correlate logs and metrics, and collect usage data to point ARR.

[gaantunes]

Honestly besides the cluster label I do not see we adding any new one.

[github-actions]

This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!