diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-02-08 07:31:03 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-02-08 07:31:03 +0000 |
| commit | 50485bedfd9818165aa1d039d0abe95a559134b7 (patch) | |
| tree | 79c7b08f67edcfb0c936e7a22931653b91189b9f /backends/WALKTHROUGH.md | |
| parent | Releasing debian version 1.11.1+dfsg-7. (diff) | |
| download | netdata-50485bedfd9818165aa1d039d0abe95a559134b7.tar.xz netdata-50485bedfd9818165aa1d039d0abe95a559134b7.zip | |
Merging upstream version 1.12.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'backends/WALKTHROUGH.md')
| -rw-r--r-- | backends/WALKTHROUGH.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md index b899556ab..0c330ee1a 100644 --- a/backends/WALKTHROUGH.md +++ b/backends/WALKTHROUGH.md @@ -67,7 +67,7 @@ chooses the base container images (centos:latest). After running this you should be sitting inside the shell of the container. After we have entered the shell we can install Netdata. This process could not -be easier. If you take a look at [this link](../installer/#installation), the Netdata devs give us +be easier. If you take a look at [this link](../packaging/installer/#installation), the Netdata devs give us several one-liners to install netdata. I have not had any issues with these one liners and their bootstrapping scripts so far (If you guys run into anything do share). Run the following command in your container. @@ -290,3 +290,5 @@ automatically begins to scrape them. Once achieved you do not have to think about the monitoring system until Prometheus cannot keep up with your scale. Once this happens there are options presented in the Prometheus documentation for solving this. Hope this was helpful, happy monitoring. + +[]() |