summaryrefslogtreecommitdiffstats
path: root/docs/Charts.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/Charts.md')
-rw-r--r--docs/Charts.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/Charts.md b/docs/Charts.md
index d5080ce1fe..66be03be5e 100644
--- a/docs/Charts.md
+++ b/docs/Charts.md
@@ -23,3 +23,5 @@ The reasoning behind calling these instances "families" is that different charts
A context is a grouping of identical charts, for each instance of the hardware or software monitored. For example, `health/health.d/net.conf` refers to four contexts: `net.drops`, `net.fifo`, `net.net`, `net.packets`. You can see the context of a chart if you hover over the date right above the dimensions of the chart. The line that appears shows you two things: the collector that produces the chart and the chart context.
For example, let's take the `net.packets` context. You will see on the dashboard as many charts with context net.packets as you have network interfaces (families). These charts will be named `net_packets.[family]`. For the example of the two interfaces `eth0` and `eth1`, you will see charts named `net_packets.eth0` and `net_packets.eth1`. Both of these charts show the exact same dimensions, but for different instances of a network interface.
+
+[![analytics](https://www.google-analytics.com/collect?v=1&aip=1&t=pageview&_s=1&ds=github&dr=https%3A%2F%2Fgithub.com%2Fnetdata%2Fnetdata&dl=https%3A%2F%2Fmy-netdata.io%2Fgithub%2Fdocs%2FCharts&_u=MAC~&cid=5792dfd7-8dc4-476b-af31-da2fdb9f93d2&tid=UA-64295674-3)]()