brucewu16899 / docker-netdata

netdata monitoring tool on Alpine Linux

docker-netdata

thanks titpetric netdata monitoring tool on Alpine Linux

Netdata monitors your server with thoughts of performance and memory usage, providing detailed insight into very recent server metrics. It's nice, and now it's also dockerized.

More info about project: https://github.com/firehol/netdata

Using

docker run -d --cap-add SYS_PTRACE \
           -v /proc:/host/proc:ro \
           -v /sys:/host/sys:ro \
           -p 19999:19999 babim/netdata

Open a browser on http://server:19999/ and watch how your server is doing.

Getting emails on alarms

Netdata supports forwarding alarms to an email address. You can set up sSMTP by setting the following ENV variables:

• SSMTP_TO - This is the address alarms will be delivered to.
• SSMTP_SERVER - This is your SMTP server. Defaults to smtp.gmail.com.
• SSMTP_PORT - This is the SMTP server port. Defaults to 587.
• SSMTP_USER - This is your username for the SMTP server.
• SSMTP_PASS - This is your password for the SMTP server. Use an app password if using Gmail.
• SSMTP_TLS - Use TLS for the connection. Defaults to YES.
• SSMTP_HOSTNAME - The hostname mail will come from. Defaults to localhost.

For example, using gmail:

-e [email protected] -e SSMTP_USER=user -e SSMTP_PASS=password

Alternatively, if you already have s sSMTP config, you can use that config with:

-v /path/to/config:/etc/ssmtp

See the following link for details on setting up sSMTP: SSMTP - ArchWiki

Environment variables

It's possible to pass a NETDATA_PORT environment variable with -e, to start up netdata on a different port.

docker run -e NETDATA_PORT=80 [...]

Some explanation is in order

Docker needs to run with the SYS_PTRACE capability. Without it, the mapped host/proc filesystem is not fully readable to the netdata deamon, more specifically the "apps" plugin:

16-01-12 07:58:16: ERROR: apps.plugin: Cannot process /host/proc/1/io (errno 13, Permission denied)

See the following link for more details: /proc/1/environ is unavailable in a container that is not priviledged

Limitations

In addition to the above requirements and limitations, monitoring the complete network interface list of the host is not possible from within the Docker container. If you're running netdata and want to graph all the interfaces available on the host, you will have to use --net=host mode.

See the following link for more details: network interfaces missing when mounting proc inside a container