Tutorials

Some Design Templates

All-In-One Test Environment

docker-compose

Above diagram shows the overview of the autobuild output. running ./autobuild.sh creates multiple containers:

  • a dnsmonster container per selected interfaces from the host to look at the raw traffic. Host’s interface list will be prompted when running autobuild.sh, allowing you to select one or more interfaces. *a clickhouse container to collect dnsmonster’s outputs and save all the logs and data to their respective directory inside the host. Both paths will be prompted in autobuild.sh. The default tables and TTL for them will implemented automatically.
  • a grafana container connecting back to clickhouse. It automatically sets up the connection to ClickHouse, and sets up the builtin dashboards based on the default ClickHouse tables. Note that Grafana container needs an internet connection to successfully set up the plugins. If you don’t have an internet connection, the dnsmonster and clickhouse containers will start working without any issues, and the error produced by Grafana can be ignored.

All-in-one Demo

AIO Demo


ClickHouse Cloud

use dnsmonster with ClickHouse Cloud

Kubernetes

use dnsmonster to monitor Kubernetes DNS traffic

Last modified April 15, 2022: copied the sample tutorial to docs (b1b27fc)