Skip to Content
ConnectorsDocker logs

Docker logs — docker_logs

Tails a running container’s logs, one event per line — all lines by default, with optional match/drop regex filters. Supports discovery, and the dedicated discover_docker tool scans the whole local Docker environment for candidate containers.

Prerequisites: access to the Docker daemon — run navflowd on the host, or mount the Docker socket and include the Docker CLI in the image.

Set up

Ask a connected agent:

Use navflow to find my running containers and ingest the api-server’s logs.

The agent calls discover_docker (scans running containers, proposes one source per candidate) or discover_source for a known container, test_source (dry-run — tails a few lines), then create_source.

Configuration

fieldtypedescription
container*stringcontainer (or compose service) name
compose_filestringpath to docker-compose.yml if the container runs under Compose
matchstringkeep only lines matching this regex (default: all), e.g. ERROR|WARN
dropstringskip lines matching this regex, e.g. HTTP/1.1" to drop access logs
label_patternstringregex with named groups → per-line label context

Verify

Open the source in the console: Recent events shows lines on the next poll. If nothing arrives, check that navflowd can run docker logs <container> — the same access it needs.

Last updated on