diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2022-04-14 18:12:10 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2022-04-14 18:12:10 +0000 |
| commit | b5321aff06d6ea8d730d62aec2ffd8e9271c1ffc (patch) | |
| tree | 36c41e35994786456154f9d3bf88c324763aeea4 /docs/why-netdata | |
| parent | Adding upstream version 1.33.1. (diff) | |
| download | netdata-b5321aff06d6ea8d730d62aec2ffd8e9271c1ffc.tar.xz netdata-b5321aff06d6ea8d730d62aec2ffd8e9271c1ffc.zip | |
Adding upstream version 1.34.0.upstream/1.34.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'docs/why-netdata')
| -rw-r--r-- | docs/why-netdata/1s-granularity.md | 2 | ||||
| -rw-r--r-- | docs/why-netdata/README.md | 2 | ||||
| -rw-r--r-- | docs/why-netdata/immediate-results.md | 2 | ||||
| -rw-r--r-- | docs/why-netdata/meaningful-presentation.md | 2 | ||||
| -rw-r--r-- | docs/why-netdata/unlimited-metrics.md | 2 |
5 files changed, 5 insertions, 5 deletions
diff --git a/docs/why-netdata/1s-granularity.md b/docs/why-netdata/1s-granularity.md index a2cc65b8f..4fc7fab2d 100644 --- a/docs/why-netdata/1s-granularity.md +++ b/docs/why-netdata/1s-granularity.md @@ -56,4 +56,4 @@ Netdata has been designed to: So, for Netdata 1s granularity is easy, the natural outcome... -[](<>) + diff --git a/docs/why-netdata/README.md b/docs/why-netdata/README.md index 39cda51e2..c482ee944 100644 --- a/docs/why-netdata/README.md +++ b/docs/why-netdata/README.md @@ -32,4 +32,4 @@ Netdata's helps us troubleshoot slowdowns without touching the console. So, everything is a bit different. -[](<>) + diff --git a/docs/why-netdata/immediate-results.md b/docs/why-netdata/immediate-results.md index ba7c7d684..b35aa5381 100644 --- a/docs/why-netdata/immediate-results.md +++ b/docs/why-netdata/immediate-results.md @@ -43,4 +43,4 @@ Netdata: - Does not introduce any query languages or any other technology to be learned. Of course some familiarity with the tool is required, but nothing too complicated. - Includes all the community expertise and experience for monitoring systems and applications. -[](<>) + diff --git a/docs/why-netdata/meaningful-presentation.md b/docs/why-netdata/meaningful-presentation.md index 64d83b4f6..fc670e33f 100644 --- a/docs/why-netdata/meaningful-presentation.md +++ b/docs/why-netdata/meaningful-presentation.md @@ -65,4 +65,4 @@ But it simplifies everything else. Data collection, metrics database and visuali Netdata goes a step further, by enriching the dashboard with information that is useful for most people. So, to improve clarity and help users be more effective, Netdata includes right in the dashboard the community knowledge and expertise about the metrics. So, that Netdata users can focus on solving their infrastructure problem, not on the technicalities of data collection and visualization. -[](<>) + diff --git a/docs/why-netdata/unlimited-metrics.md b/docs/why-netdata/unlimited-metrics.md index 8e50062c7..b79a4ede3 100644 --- a/docs/why-netdata/unlimited-metrics.md +++ b/docs/why-netdata/unlimited-metrics.md @@ -46,4 +46,4 @@ Due to Netdata's distributed nature, the number of metrics collected does not ha Of course, since Netdata is also about [meaningful presentation](meaningful-presentation.md), the number of metrics makes Netdata development slower. We, the Netdata developers, need to have a good understanding of the metrics before adding them into Netdata. We need to organize the metrics, add information related to them, configure alarms for them, so that you, the Netdata users, will have the best out-of-the-box experience and all the information required to kill the console for troubleshooting slowdowns. -[](<>) + |