Container tag/name prefix #3569
Replies: 1 comment
-
Hey, I'm experiencing the exact same issue and just wanted to explain my use case I have a Grafana dashboard along with cAdvisor running on my server where Coolify is set up. cAdvisor exports CPU/RAM usage metrics for each container individually. Here’s a quick screenshot: As you can see, it's impossible to identify anything with these auto-generated container names. So yeah, I was thinking about 2 solutions:
I think both solutions would be useful to have. In fact, the second one might be more practical in some cases: it would allow me to get consistent metrics for a single container, even if it restarts and gets a new name. With the labels, the values would remain the same even if it restart, allowing me to maintain a continuous series instead of having two separate series labeled I would be happy to submit a PR if we get the go-ahead for this. Also, on top of that, we also have an issue with managed DBs, where we can't edit container names at all. Unfortunately I don't know enough about Coolify's inner workings to suggest a solution here. |
Beta Was this translation helpful? Give feedback.
-
It would be nice to prefix containers with a tag so we can identify containers without losing the rollback functionality.
We use datadog across our coolify servers and it would help with identifying containers and what they are serving.
I am aware we can force name the containers, but at the cost of rolling deployments etc. Instead it would be great if we could supply a prefix and a random string is postfixed to the container name to keep the rolling deployment feature intact.
Beta Was this translation helpful? Give feedback.
All reactions