Skip to main content

Deployment Guides

Get Netdata up and running in your infrastructure. Choose a deployment method that fits your needs.

Quick Start​

Getting Started

Deployment Methods​

Standalone​

A Netdata Agent that collects, stores, alerts and serves dashboards on its own, with or without a Parent. Every Agent is a complete observability node.

Best for: Evaluation, single systems, isolated sites, or any node that must keep working on its own

Setup time: < 1 minute

→ Deploy Standalone Agent

The recommended production setup. Stream metrics from Child Agents to centralized Parent nodes for better data persistence and resource optimization.

Best for: Production environments of any size, high availability requirements

Setup time: 10-15 minutes

→ Deploy Parent-Child Setup

Kubernetes​

Deploy Netdata across your Kubernetes clusters with our Helm chart. Required for proper Kubernetes monitoring.

Best for: Kubernetes environments (required for full K8s observability)

Setup time: 5-10 minutes

→ Deploy on Kubernetes

Docker​

Run Netdata in containers for quick testing. Note: Some features are limited compared to host installation.

Best for: Quick testing, ephemeral environments

Setup time: 2-5 minutes

→ Deploy with Docker

Which Deployment Should I Choose?​

EnvironmentRecommended MethodWhy
Production serversParent-ChildBest data persistence, resource optimization, and high availability
KubernetesHelm ChartRequired for K8s API access and pod metadata collection
Testing/DevelopmentStandalone or DockerQuick to set up and remove
Single serverStandalone (upgrade to Parent-Child later)Fully functional on its own; add a Parent for centralization
Important Notes
  • Kubernetes: Always use our Helm chart. Direct host installation won't have access to K8s API for pod metadata and service discovery.
  • Docker: Limited feature set compared to host installation. Best for testing, not recommended for production.
  • Production: Parent-Child is recommended regardless of cluster size for better reliability and data persistence.

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.