get-started.mdx 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. ---
  2. title: "Get started with Netdata"
  3. description: "Download and install the open-source Netdata monitoring agent on physical/virtual servers, Linux (Ubuntu/Debian/CentOS/etc), Docker, Kubernetes, and many others, often with one command."
  4. type: how-to
  5. sidebar_label: "Get started"
  6. custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/get-started.mdx
  7. ---
  8. import { OneLineInstallWget } from '../src/components/OneLineInstall/'
  9. import { Install, InstallBox } from '../src/components/Install/'
  10. # Get started with Netdata
  11. Netdata is a free and open-source (FOSS) monitoring agent that collects thousands of hardware and software metrics from
  12. any physical or virtual system (we call them _nodes_). These metrics are organized in an easy-to-use and -navigate interface.
  13. Together with [Netdata Cloud](https://learn.netdata.cloud/docs/cloud), you can monitor your entire infrastructure in
  14. real time and troubleshoot problems that threaten the health of your nodes.
  15. Netdata runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices. It
  16. runs on Linux distributions (Ubuntu, Debian, CentOS, and more), container/microservice platforms (Kubernetes clusters,
  17. Docker), and many other operating systems (FreeBSD, macOS), with no `sudo` required.
  18. ## Install on Linux with one-line installer
  19. The **recommended** way to install Netdata on a Linux node (physical, virtual, container, IoT) is our one-line
  20. [kickstart script](/packaging/installer/methods/kickstart.md). This script automatically installs dependencies and
  21. builds Netdata from its source code.
  22. Copy the script, paste it into your node's terminal, and hit `Enter` to begin the installation process.
  23. <OneLineInstallWget />
  24. Jump down to [what's next](#whats-next) to learn how to view your new dashboard and take your next steps monitoring and
  25. troubleshooting with Netdata.
  26. ## Other installation options
  27. <Install>
  28. <InstallBox
  29. to="/docs/agent/packaging/docker"
  30. os="Run with Docker"
  31. svg="docker" />
  32. <InstallBox
  33. to="/docs/agent/packaging/installer/methods/kubernetes"
  34. os="Deploy on Kubernetes"
  35. svg="kubernetes" />
  36. <InstallBox
  37. to="/docs/agent/packaging/installer/methods/macos"
  38. os="Install on macOS"
  39. svg="macos" />
  40. <InstallBox
  41. to="/docs/agent/packaging/installer/methods/manual"
  42. os="Linux from Git"
  43. svg="linux" />
  44. <InstallBox
  45. to="/docs/agent/packaging/installer/methods/source"
  46. os="Linux from source"
  47. svg="linux" />
  48. <InstallBox
  49. to="/docs/agent/packaging/installer/methods/offline"
  50. os="Linux for offline nodes"
  51. svg="linux" />
  52. </Install>
  53. ## What's next?
  54. To start using Netdata, open a browser and navigate to `http://NODE:19999`, replacing `NODE` with either `localhost` or
  55. the hostname/IP address of a remote node.
  56. Where you go from here is based on your use case, immediate needs, and experience with monitoring and troubleshooting.
  57. ### Dashboard
  58. Learn more about [how the dashboard works](/docs/dashboard/how-dashboard-works.mdx), or dive directly into the many ways
  59. to [interact with charts](/docs/dashboard/interact-charts.mdx).
  60. ### Configuration
  61. Discover the recommended way to [configure Netdata's settings or behavior](/docs/configure/nodes.md) using our built-in
  62. `edit-config` script, then apply that knowledge to mission-critical tweaks, such as [changing how long Netdata stores
  63. metrics](/docs/store/change-metrics-storage.md).
  64. ### Data collection
  65. If Netdata didn't autodetect all the hardware, containers, services, or applications running on your node, you should
  66. learn more about [how data collectors work](/docs/collect/how-collectors-work.md). If there's a [supported
  67. collector](/collectors/COLLECTORS.md) for metrics you need, [configure the collector](/docs/collect/enable-configure.md)
  68. or read about its requirements to configure your endpoint to publish metrics in the correct format and endpoint.
  69. ### Alarms & notifications
  70. Netdata comes with hundreds of preconfigured alarms, designed by our monitoring gurus in parallel with our open-source
  71. community, but you may want to [edit alarms](/docs/monitor/configure-alarms.md) or [enable
  72. notifications](/docs/monitor/enable-notifications.md) to customize your Netdata experience.
  73. ### Need to monitor multiple nodes in one place?
  74. For robust multi-node monitoring from a single interface, consider [Netdata
  75. Cloud](https://learn.netdata.cloud/docs/cloud), which streams, aggregates, and visualizes metrics from any number of
  76. nodes. It's all the same out-of-the-box, zero-configuration functionality of the open-source monitoring agent, but for
  77. any number of distributed nodes, _entirely for free_.
  78. There is an alternative for those who aren't interested in using Netdata Cloud, albeit with some required configuration.
  79. Each node can [stream](/streaming/README.md) its metrics to any other node, and the default
  80. [registry](/registry/README.md) is configurable to create a private "network" of Netdata dashboards.