Is your change request related to a problem? Please describe.
Instances of a service can be grouped into pools. For example, a service could be split into two pools: canary and default. Canary being a small pool that is deployed before default to check that everything is working as expected. Some pools can also be test pools of one or two instances to test a change in production.
The metrics can be aggregated by pool to easily compare the canary and default pools but currently there is no standard labels for that concept.
Describe the solution you'd like
A new label service.instance.pool which designates the pool the instance is part of. The value would depend on the company but some recommended values would be:
default
canary
test-1
test-2
Describe alternatives you've considered
service.instance.pool.name in case a pool can have other fields, such as an id + name
service.pool but I think it makes more sense to add it at the instance level
Area(s)
area:service
Is your change request related to a problem? Please describe.
Instances of a service can be grouped into pools. For example, a service could be split into two pools:
canaryanddefault. Canary being a small pool that is deployed before default to check that everything is working as expected. Some pools can also be test pools of one or two instances to test a change in production.The metrics can be aggregated by pool to easily compare the canary and default pools but currently there is no standard labels for that concept.
Describe the solution you'd like
A new label
service.instance.poolwhich designates the pool the instance is part of. The value would depend on the company but some recommended values would be:defaultcanarytest-1test-2Describe alternatives you've considered
service.instance.pool.namein case a pool can have other fields, such as an id + nameservice.poolbut I think it makes more sense to add it at the instance leveldeployment.poolAdditional context
No response