search

coroot / coroot

Coroot is an open-source APM & Observability tool, a DataDog and NewRelic alternative 📊, 🖥️, 👉. Powered by eBPF for rapid insights into system performance. Monitor, analyze, and optimize your infrastructure effortlessly for peak reliability at any scale.
https://coroot.com
Apache License 2.0
5.32k stars 212 forks source link

Lost service mapped when ip changes #113

Open xhit opened 11 months ago

xhit commented 11 months ago

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 commented 11 months ago

@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 commented 11 months ago

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 commented 9 months ago

Any updates? I have simmilar issues with map.

image

external for internal communications...

binali-rustamov commented 9 months ago

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".