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

Lost service mapped when ip changes #113

Open
xhit opened this issue Nov 16, 2023 · 4 comments
Open

Lost service mapped when ip changes #113

xhit opened this issue Nov 16, 2023 · 4 comments

Comments

@xhit
Copy link

xhit commented Nov 16, 2023

See this image:

image

The service external http is a Docker swarm service that IP was changed, then, we now had this new "external service" and the real service has metrics from ip change.

Also, from all these external services, only the external mongodb is in the Health tab. I don't know if it's expected but I think that should be all or none or these.

@apetruhin
Copy link
Member

@xhit,
I'm not sure I understand what has been lost. Could you please provide before-and-after screenshots?

You can append ?from=now-2d&to=now-1d (or similar parameters) to the URL to navigate to the past.

@xhit
Copy link
Author

xhit commented Nov 17, 2023

In the image, the service svc ns:general-auth in yellow it's the same as external http, after a restart of the service all new metrics is displayed on external http. After restart, ip changes, but it's in same network.

Note that this it's a test server, all services are in same Docker swarm manager node without replicas.

image

@binali-rustamov
Copy link

Any updates? I have simmilar issues with map.

image

external for internal communications...

@binali-rustamov
Copy link

binali-rustamov commented Jan 29, 2024

Found that when I start coroot-node-agent for the first time, I don't get container_net_tcp_listen_info for the current version of docker swarm stack services.
image

I'm getting container_net_tcp_listen_info after redeploying my Docker Swarm services, but after some time, I see that situation is happening again "missing container_net_tcp_listen_info".

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

3 participants