memory used bug

[artem-kostylev]

To Reproduce

1. Deploy Elasticsearch using Docker Compose

Current vs. Expected behavior

I expect that all used resources will be displayed in /dashboard/monitoring, but for some reason, the resources consumed by Elasticsearch are not showing up.

1.mp4

Provide environment information

Dokploy: v0.10.10
VPS: Linode

Which area(s) are affected? (Select all that apply)

Docker Compose

Additional context

I tested on vultr and linode

[AprilNEA]

Having the same problem

[Siumauricio]

I think the monitoring part needs to be redesigned, to make it more advanced, this is something I want to improve.

currently we use docker stats, which is the information provided by docker to monitor the resources, however it seems that in certain cases the information is applied but is not reflected in the information transmitted by docker stats.

[henriklovhaug]

You could maybe do this? docker stats --no-stream --format '{{.MemPerc}}' | awk '{o+=$1} END {print o}'.

I assume every docker process is controlled by Dokploy