feat: add some new labels to every container

[Julien-R44]

Changes

I strongly encourage to read the comment that initiated this PR: #3569 (comment)

TL;DR: The main issue is the difficulty in monitoring due to automatically generated container names. Currently, when I look at my Grafana/cAdvisor dashboard tracking CPU usage for each container managed by Coolify, I only see cuid names , which makes it impossible to identify what each container corresponds to.

So we need a way to have "human-readable" names for each container. This PR addresses the issue by adding three new labels to each container managed by Coolify :

• coolify.resourceName: The name of the Application or Service
• coolify.projectName: The name of the project where the resource lives
• coolify.serviceName: This one might be a bit confusing, and perhaps we can find a better name. If the resource is of type Service, it will be the sub-service name. If it's of type Application, it will be the application name. This label is necessary because, using my monitoring use case as an example, I need metrics/logs for each of my containers. To differentiate them, I need a unique name. If I'm using a Service, I can't rely on coolify.resourceName since all the services in my docker-compose file would have the same value. I hope this explanation makes sense.

This is my first contribution to Coolify, and I'm not familiar with PHP either, so feel free to point out any corrections or improvements I should made

( And thanks a lot for making Coolify 💙 )

Issues

• Container tag/name prefix #3569

[peaklabs-dev]

I get why this would be needed overall but I have a questions:

1. Why does it have to be docker labels and not env variabels as we do have those COOLIFY_CONTAINER_NAME for example? And I will soon be adding things like Project name and so on as well to env vars.

[Julien-R44]

Because environment variables aren't collected by cAdvisor or anything I think. I suppose there's a way to tweak something, but with labels it works straight away. cAdvisor collects them, and I can use them in my PromQL queries ( Prometheus )