[Heartbeat] Docker autodiscovery generates monitors for non-published ports

[eigengrau]

We are running a scheduled container environment (Nomad), so I was looking into leveraging the Docker autodiscovery provider to set up monitors dynamically (Heartbeat 7.0.1 run inside Docker with host networking). However, it appears that when a container exposes a port, but that port is not published, the Docker autodiscovery provider will still set up a monitor. This monitor will then permanently report failure due to the port not being reachable.

It would be convenient if monitors would not be set up unless the corresponding port is published to the host. Alternatively, it would be useful if the discovery data included a flag indicating whether the container port is published, so that the configured autodiscovery template could filter such containers using a conditional.

[elasticmachine]

Pinging @elastic/uptime

[andrewvc]

@exekias would be curious to hear your thoughts on this.

[exekias]

This sounds like a reasonable ask, this is where all this happens:

beats/libbeat/autodiscover/providers/docker/docker.go

Line 228 in 3ab727b

"port": port.PrivatePort,

, we could add more data to Docker events, may be publicport and privateport fields? That would give enough info to make distinctions

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.