-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hubble UI does not pick service name correctly #721
Comments
I have the same problem, I will like to be able to split them visually. |
From testing I see that the name is taken from the label Although that value is not configurable in some helm charts. Is there a way to choose which label is to be used for the name displayed in the UI? |
Could you guys please post all the labels for those services? |
@yandzee I have these labels:
only difference on each service is the component label |
Hi, I am running thanos and prometheus on a kind cluster using the helm chart as described here -> https://github.com/bitnami/charts/tree/main/bitnami/thanos#integrate-thanos-with-prometheus-and-alertmanager
In the hubble UI, how is the naming of the service picked up in the UI? There are different components for thanos like ruler, query, storegateway but all are marked as thanos.
https://github.com/bitnami/charts/blob/9c3dfb522ac8b14c5325c2f4077d171d3d0c84aa/bitnami/thanos/templates/query/service.yaml#L11
there is a service name defined
The text was updated successfully, but these errors were encountered: