Replies: 1 comment
-
Same here, would be nice |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Further to this discussion,
#1132
Could we have the capture agent monitor containers on the host capture is running on?
I have several hosts running capture and I'd like to monitor all the containers across the fleet, not just the one hosting the server instance.
I'd prefer not to separately expose the docker API via http(s) but if that's the easiest way to connect to multiple docker hosts I'd rather have that than nothing.
Alternately is there a way to monitor multiple docker sockets on the checkmate server?
I have in the past used an unholy combination of mounts and tunnelling programs like spiped or stunnel to forward from one host to another and only exposing as a unix socket on the destination host.
If it was possible to monitor multiple socket files this would be a viable if clunky workaround.
I'll gratefully take any options you’re willing to develop.
Beta Was this translation helpful? Give feedback.
All reactions