Container monitoring - can they be "agent initiated"?

Hi all

Have a server with docker containers that we of course want to have monitored. With a normal linux agent you can choose in what direction the traffic should go, but can you choose traffic direction with docker monitoring?

The server is on DMZ so we don't want to punch a hole in the inward direction on the firewall.

(Bonus question: how is the container monitoring architecture built? Is it stand alone from agent or is traffic going via the agent? Then I guess we could choose traffic direction. But I don't see a requirement on agent installed, just that the node is monitored.)

Find more posts tagged with

Linux

Agent

ports

firewall

docker

container

Accepted answers

All comments

jm_sysadmin

I may be mistaken, but I think traffic starts with a container running on your DMZ server, that container gets the data from the others, and sends it to Orion.

https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Container-Supported-Environments.htm

Seashore

I suspect that to but was hoping I was wrong.
A better architecture had been that the "container pluggin" had been delivering data to the agent who transfered it to Orion in normal fashion. (in either direction)