For some reason junior devs / SREs always go nuts putting things into labels, I guess it's the same insecurity and/or brain rot of only-one-class-per-file or three-package deep source hierarchies for a total 1k line project.
The rule of thumb I give them is that if it doesn't make dimensional sense to average across across them, never use a label.
If a service which provides metrics supports multiple tenants wouldn't those metrics at the very least need a label to indicate which tenant the metrics are for?
The rule of thumb I give them is that if it doesn't make dimensional sense to average across across them, never use a label.