Tutorials

End-to-end walkthroughs — the all-in-one test environment, ClickHouse Cloud and Kubernetes.

All-in-one test environment

Running ./autobuild.sh from the repository root creates several containers:

• A dnsmonster container per selected host interface, looking at raw traffic. The host’s interface list is prompted when running autobuild.sh, so you can select one or more.
• A clickhouse container collecting dnsmonster’s output and saving logs and data to their respective directories on the host. Both paths are prompted by autobuild.sh. The default tables and their TTL are created automatically.
• A grafana container connected back to clickhouse. It sets up the ClickHouse connection and the built-in dashboards for the default tables. Grafana needs an internet connection to install its plugins — without one, dnsmonster and clickhouse still work fine and the Grafana error can be ignored.

Demo

Next

• ClickHouse Cloud — serverless ClickHouse, tables, dictionaries and Grafana.
• Kubernetes — a dnstap logger in coredns feeding a dnsmonster pod.

In this section

• ClickHouse Cloud Run dnsmonster against a serverless ClickHouse Cloud cluster — replicated tables, dictionaries and the Grafana dashboard.
• Kubernetes Inject a dnstap logger into coredns and receive the logs in a dnsmonster pod inside the same namespace.