You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I love the Pulse concept for Proxmox and I use it intensively on my infrastructure.
The docker host monitoring is also a nice concept, but in my use case it will be too verbose.
I'm working on 4 docker SwarmMode clusters with 6 nodes each, and an average of 30 stacks (or 150 containers ) on each cluster.
So when i start the agent on each node I receive a lot of (non) information and a flood of notifications because the number of exited or moving container is very high.
And in this configuration i need to stop all agents.
But your idea is really amazing and i feel that we can tune it. So i had a look on your code and i have some remarks .
First of all split the code between the core system and the agent and create his own repo. In this case we can fork the agent code and propose some PR just for this.
More idea at the agent level
allow to chose the type of monitored container (in my case, running but not paused or exited)
allow to monitor the service and/or the task level when agent is running in swarm environment
allow to modify the agent reaction when we work in global or manager mode
I think I can help you at this level, but in this case the code split is really mandatory ... and can help if you invent more agent
Thank you for this nice product.
Hope i can help you deeper in the swarm monitoring
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, I love the Pulse concept for Proxmox and I use it intensively on my infrastructure.
The docker host monitoring is also a nice concept, but in my use case it will be too verbose.
I'm working on 4 docker SwarmMode clusters with 6 nodes each, and an average of 30 stacks (or 150 containers ) on each cluster.
So when i start the agent on each node I receive a lot of (non) information and a flood of notifications because the number of exited or moving container is very high.
And in this configuration i need to stop all agents.
But your idea is really amazing and i feel that we can tune it. So i had a look on your code and i have some remarks .
First of all split the code between the core system and the agent and create his own repo. In this case we can fork the agent code and propose some PR just for this.
More idea at the agent level
I think I can help you at this level, but in this case the code split is really mandatory ... and can help if you invent more agent
Thank you for this nice product.
Hope i can help you deeper in the swarm monitoring
Best regards
Beta Was this translation helpful? Give feedback.
All reactions