What's configured out of the box
The one-click deployment starts the Netdata agent container with health checks and hundreds of default alert rules already active — there's no separate database to install, since Netdata stores its metrics locally on disk rather than in an external DB. Auto-detection begins scanning for running services (web servers, databases, containers) immediately after the container starts, and per-second charts populate within moments. For full container-level visibility, the agent needs access to the host's /proc, /sys, and Docker socket, which the template mounts automatically as part of the deployment.
First access
Open the dashboard by pointing your browser at the server's IP address on the assigned port — by default Netdata listens on port 19999, though the exact port exposed by the Leneex panel may differ. Unlike most self-hosted apps, Netdata's local dashboard has no login screen by default — anyone who can reach the port sees the metrics, which is why restricting access at the firewall or reverse-proxy level matters before you consider the deployment finished.
Connecting to Netdata Cloud (optional)
If you want a centralized view across multiple servers, you can claim the agent into a Netdata Cloud account using a claim token generated from the Cloud dashboard; this step is entirely optional and the local dashboard keeps working with or without it.