Kubernetes services gets new service ID

[RuN3]

Hello!

We experience that kubernetes services gets new SERVICE-ID from time to time, destroying the metrics and dashboards that depend on them. Aswell as wiping key requests etc. is there a good way to handle this in any way?

[kobecharles · Accepted solution]

From the dashboarding-side you could create data-explorer tiles in your dashboard with an entitly selector where you filter for the wanted services. For Example:

builtin:service.response.time:filter(and(in("dt.entity.service",entitySelector("type(service),entityName(~"IAM PDP service~")")))):splitBy():avg:auto:sort(value(avg,descending)):limit(10)

Then you would avoid the id handing completely, it's a possible work around depending on your use case. However, I'm curious as to why there are new services from time to time. When do you notice this occurs?