diff options
| author | Markos Fountoulakis <44345837+mfundul@users.noreply.github.com> | 2019-01-05 23:39:31 +0200 |
|---|---|---|
| committer | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2019-01-05 22:39:31 +0100 |
| commit | 74fd89d0d16b6aa69bf3b6987b4c8725fe8ca463 (patch) | |
| tree | 869386b613e954eaafb2bbc9f90e9d567fa62274 | |
| parent | be7daa0fbd1400a55bec5e473527daeb82fe9150 (diff) | |
Update Charts.md (#5124)
Hardware and software is uncountable, we should avoid phrases like "a hardware"
| -rw-r--r-- | docs/Charts.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Charts.md b/docs/Charts.md index 66be03be5e..64c36302f6 100644 --- a/docs/Charts.md +++ b/docs/Charts.md @@ -14,7 +14,7 @@ Most charts depict more than one dimensions. The dimensions of a chart are calle ## Families -When you have several instances of a monitored hardware or software (e.g. network interfaces, mysql instances etc.), you need to be able to identify each one separately. Netdata uses "families" to identify such instances. For example, if I have the network interfaces `eth0` and `eth1`, `eth0` will be one family, and `eth1` will be another. +When you have several instances of a monitored hardware or software resource (e.g. network interfaces, mysql instances etc.), you need to be able to identify each one separately. Netdata uses "families" to identify such instances. For example, if I have the network interfaces `eth0` and `eth1`, `eth0` will be one family, and `eth1` will be another. The reasoning behind calling these instances "families" is that different charts for the same instance can and many times are related (relatives, family, you get it). The family of a chart is usually the name of the netdata dashboard submenu that you see selected on the right navigation pane, when you are looking at a chart. For the example of the two network interfaces, you would see a submenu `eth0` and a submenu `eth1` under the "Network Interfaces" menu on the right navigation pane. |