Skip to content
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

why can't get service map #42

Closed
tripitakav opened this issue May 5, 2023 · 11 comments
Closed

why can't get service map #42

tripitakav opened this issue May 5, 2023 · 11 comments

Comments

@tripitakav
Copy link

image
image

@apetruhin
Copy link
Member

@tripitakav

  • Which Coroot and coroot-node-agent versions are you using?
  • Are there any errors in the logs?

@tripitakav
Copy link
Author

@tripitakav

  • Which Coroot and coroot-node-agent versions are you using?
  • Are there any errors in the logs?
  1. Coroot: v0.16.2 Node-agent:v1.7.6

image
image
There are no errors in the logs

@apetruhin
Copy link
Member

Can you please share the output of the following Prometheus query?

node_info

@tripitakav
Copy link
Author

Can you please share the output of the following Prometheus query?

node_info

image

@apetruhin
Copy link
Member

We suspect that there are some issues with the way metrics are being relabeled, such as incorrect or missing labels.

Is this the right data source? The number of nodes doesn't match:

image

versus

image

@tripitakav
Copy link
Author

I also think it should be due to incorrect or missing labels, because I deployed Coroot two months ago and everything was normal at that time. Then I deleted the namespace, and recently I had this issue when I was redeploying to demonstrate to the leader。

The data source is right,I'm just checking for node_info when selecting the metric, I chose staging-eks because the labels for both staging-eks and prod-hk metric are similar. Because I have deleted the prod-hk metric, only staging-eks have

@apetruhin
Copy link
Member

@tripitakav
Let's check some other metric labels. One or two samples of each query will be enough:

  1. kube_node_info
  2. kube_pod_info
  3. container_info

@apetruhin
Copy link
Member

apetruhin commented May 12, 2023

@tripitakav
We guess that the metrics from kube-state-metrics (e.g., kube_pod_info, kube_pod_labels) no longer include the uid label after the relabeling process. Coroot needs this label to load application instances.

@tripitakav
Copy link
Author

@tripitakav Let's check some other metric labels. One or two samples of each query will be enough:

  1. kube_node_info
  2. kube_pod_info
  3. container_info

image
2.
image
3.
image

@tripitakav
Copy link
Author

@tripitakav We guess that the metrics from kube-state-metrics (e.g., kube_pod_info, kube_pod_labels) no longer include the uid label after the relabeling process. Coroot needs this label load application instances.

Yes,it don't has label include uid

@apetruhin
Copy link
Member

Consider removing the rule that drops the uid label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants