Docs: Change MacOS to macOS (#8562)
* Change MacOS to macOS * Change Mac as noun to macOS system
Joel Hans committed
Apr 6, 2020 at 07:35 UTC
23f9bd56913f63f4e116d950bd787d5d23419153
13 files changed
+24
-14
README.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Netdata"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/README.md
6
---
7
-->
@@ -33,7 +34,7 @@ granularity. Run this long-term storage autonomously, or integrate Netdata with
34
Netdata is **fast** and **efficient**, designed to permanently run on all systems (**physical** and **virtual** servers,
35
**containers**, **IoT** devices), without disrupting their core function.
36
36
-Netdata is **free, open-source software** and it currently runs on **Linux**, **FreeBSD**, and **MacOS**, along with
37
+Netdata is **free, open-source software** and it currently runs on **Linux**, **FreeBSD**, and **macOS**, along with
38
other systems derived from them, such as **Kubernetes** and **Docker**.
39
40
Netdata is not hosted by the CNCF but is the 3rd most starred open-source project in the [Cloud Native Computing
build_external/README.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "External build-system"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/build_external/README.md
6
---
7
-->
@@ -9,7 +10,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/build_external/R
10
11
This wraps the build-system in Docker so that the host system and the target system are
12
decoupled. This allows:
12
-* Cross-compilation (e.g. linux development from MacOS)
13
+* Cross-compilation (e.g. linux development from macOS)
14
* Cross-distro (e.g. using CentOS user-land while developing on Debian)
15
* Multi-host scenarios (e.g. master/slave configurations)
16
* Bleeding-edge sceneraios (e.g. using the ACLK (**currently for internal-use only**))
collectors/COLLECTORS.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Supported collectors list"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/COLLECTORS.md
6
---
7
-->
@@ -37,7 +38,7 @@ collector—we may be looking for contributions from users such as yourself!
38
| [diskspace.plugin](diskspace.plugin/README.md) | Linux | Collects disk space usage metrics on Linux mount points. |
39
| [freebsd.plugin](freebsd.plugin/README.md) | FreeBSD | Collects resource usage and performance data on FreeBSD systems. |
40
| [idlejitter.plugin](idlejitter.plugin/README.md) | any | Measures CPU latency and jitter on all operating systems. |
40
-| [macos.plugin](macos.plugin/README.md) | macos | Collects resource usage and performance data on MacOS systems. |
41
+| [macos.plugin](macos.plugin/README.md) | macos | Collects resource usage and performance data on macOS systems. |
42
| [proc.plugin](proc.plugin/README.md) | Linux | Collects resource usage and performance data on Linux systems. |
43
| [slabinfo.plugin](slabinfo.plugin/README.md) | Linux | Collects kernel SLAB details on Linux systems. |
44
| [statsd.plugin](statsd.plugin/README.md) | any | Implements a high performance `statsd` server for Netdata. |
collectors/macos.plugin/README.md
+1
-1
@@ -7,7 +7,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/macos
7
8
# macos.plugin
9
10
-Collects resource usage and performance data on MacOS systems
10
+Collects resource usage and performance data on macOS systems
11
12
By default, Netdata will enable monitoring metrics for disks, memory, and network only when they are not zero. If they are constantly zero they are ignored. Metrics that will start having values, after Netdata is started, will be detected and charts will be automatically added to the dashboard (a refresh of the dashboard is needed for them to appear though). Use `yes` instead of `auto` in plugin configuration sections to enable these charts permanently. You can also set the `enable zero metrics` option to `yes` in the `[global]` section which enables charts with zero metrics for all internal Netdata plugins.
13
daemon/config/README.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Daemon configuration"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/daemon/config/README.md
6
---
7
-->
@@ -220,7 +221,7 @@ For example, the `system.io` chart has the following default settings:
221
These `dim` settings produce two dimensions, `in` and `out`, both of which use the `incremental` algorithm. By
222
multiplying the value of `out` by -1, Netdata creates the negative values seen in the following area chart:
223
223
-
226
227
[](<>)
docs/netdata-security.md
+1
-1
@@ -81,7 +81,7 @@ You can bind Netdata to multiple IPs and ports. If you use hostnames, Netdata wi
81
82
For cloud based installations, if your cloud provider does not provide such a private LAN (or if you use multiple providers), you can create a virtual management and administration LAN with tools like `tincd` or `gvpe`. These tools create a mesh VPN allowing all servers to communicate securely and privately. Your administration stations join this mesh VPN to get access to management and administration tasks on all your cloud servers.
83
84
-For `gvpe` we have developed a [simple provisioning tool](https://github.com/netdata/netdata-demo-site/tree/master/gvpe) you may find handy (it includes statically compiled `gvpe` binaries for Linux and FreeBSD, and also a script to compile `gvpe` on your Mac). We use this to create a management and administration LAN for all Netdata demo sites (spread all over the internet using multiple hosting providers).
84
+For `gvpe` we have developed a [simple provisioning tool](https://github.com/netdata/netdata-demo-site/tree/master/gvpe) you may find handy (it includes statically compiled `gvpe` binaries for Linux and FreeBSD, and also a script to compile `gvpe` on your macOS system). We use this to create a management and administration LAN for all Netdata demo sites (spread all over the internet using multiple hosting providers).
85
86
---
87
docs/step-by-step/step-00.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "The step-by-step Netdata tutorial"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/step-by-step/step-00.md
6
---
7
-->
@@ -21,7 +22,7 @@ If you have monitoring experience, or would rather get straight into configuring
22
straight into code and configurations with our [getting started guide](../getting-started.md).
23
24
> This tutorial contains instructions for Netdata installed on a Linux system. Many of the instructions will work on
24
-> other supported operating systems, like FreeBSD and MacOS, but we can't make any guarantees.
25
+> other supported operating systems, like FreeBSD and macOS, but we can't make any guarantees.
26
27
## Where to go if you need help
28
docs/step-by-step/step-04.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Step 4. The basics of configuring Netdata"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/step-by-step/step-04.md
6
---
7
-->
@@ -61,7 +62,7 @@ an example file to your Netdata config directory and then allow you to edit it b
62
> change permanent](https://stackoverflow.com/questions/13046624/how-to-permanently-export-a-variable-in-linux).
63
64
Let's give it a shot. Navigate to your Netdata config directory. To use `edit-config` on `netdata.conf`, you need to
64
-have permissions to edit the file. On Linux/MacOS systems, you can usually use `sudo` to elevate your permissions.
65
+have permissions to edit the file. On Linux/macOS systems, you can usually use `sudo` to elevate your permissions.
66
67
```bash
68
cd /etc/netdata # Replace this path with your Netdata config directory, if different as found in the steps above
docs/tutorials/collect-unbound-metrics.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Monitor Unbound DNS servers with Netdata"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/collect-unbound-metrics.md
6
---
7
-->
@@ -11,7 +12,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/tutorials/c
12
Labs. In v1.19 of Netdata, we release a completely refactored collector for collecting real-time metrics from Unbound
13
servers and displaying them in Netdata dashboards.
14
14
-Unbound runs on FreeBSD, OpenBSD, NetBSD, MacOS, Linux, and Windows, and supports DNS-over-TLS, which ensures that DNS
15
+Unbound runs on FreeBSD, OpenBSD, NetBSD, macOS, Linux, and Windows, and supports DNS-over-TLS, which ensures that DNS
16
queries and answers are all encrypted with TLS. In theory, that should reduce the risk of eavesdropping or
17
man-in-the-middle attacks when communicating to DNS servers.
18
docs/what-is-netdata.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "What is Netdata?"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/what-is-netdata.md
6
---
7
-->
@@ -19,7 +20,7 @@ Netdata provides **unparalleled insights**, **in real-time**, of everything happ
20
21
_Netdata is **fast** and **efficient**, designed to permanently run on all systems (**physical** & **virtual** servers, **containers**, **IoT** devices), without disrupting their core function._
22
22
-Netdata is **free, open-source software** and it currently runs on **Linux**, **FreeBSD**, and **MacOS**.
23
+Netdata is **free, open-source software** and it currently runs on **Linux**, **FreeBSD**, and **macOS**.
24
25
---
26
health/REFERENCE.md
+2
-1
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Health configuration reference"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/health/REFERENCE.md
6
---
7
-->
@@ -136,7 +137,7 @@ If you create a template using the `disk.io` context, it will apply an alarm to
137
The alarm or template will be used only if the operating system of the host matches this list specified in `os`. The
138
value is a space-separated list.
139
139
-The following example enables the entity on Linux, FreeBSD, and MacOS, but no other operating systems.
140
+The following example enables the entity on Linux, FreeBSD, and macOS, but no other operating systems.
141
142
```yaml
143
os: linux freebsd macos
packaging/installer/methods/macos.md
+1
-1
@@ -75,7 +75,7 @@ sudo ./netdata-installer.sh --install /usr/local
75
> Your Netdata configuration directory will be at `/usr/local/netdata/`, and your stock configuration directory will
76
> be at **`/usr/local/lib/netdata/conf.d/`.**
77
>
78
-> The installer will also install a startup plist to start Netdata when your Mac boots.
78
+> The installer will also install a startup plist to start Netdata when your macOS system boots.
79
80
## What's next?
81
packaging/maintainers/README.md
+3
-2
@@ -1,6 +1,7 @@
1
<!--
2
---
3
title: "Package Maintainers"
4
+date: 2020-03-31
5
custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/maintainers/README.md
6
---
7
-->
@@ -36,11 +37,11 @@ This page tracks the package maintainers for Netdata, for various operating syst
37
38
---
39
39
-## MacOS
40
+## macOS
41
42
| System | URL | Core Developer | Package Maintainer
43
|:-:|:-:|:-:|:-:|
43
-| MacOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/master/Formula/netdata.rb)|@vlvkobal|@rickard-von-essen
44
+| macOS Homebrew Formula|[link](https://github.com/Homebrew/homebrew-core/blob/master/Formula/netdata.rb)|@vlvkobal|@rickard-von-essen
45
46
---
47