@cryptotaxi247 / netdata-1 / commits / 9f8dc123a

Clean netdata naming (#11484)

* replace "NetData" with "Netdata" * replace "NetData" with "Netdata"

Andrew Maguire committed Sep 4, 2021 at 16:47 UTC 9f8dc123a2a702a3014ce559c199b9f0880f61c9

21 files changed +68 -68

.github/scripts/pkg-test.sh

+4 -4

@@ -6,7 +6,7 @@ install_debian_like() {

7 apt-get update

9 - # Install NetData

9 + # Install Netdata

10 apt-get install -y /netdata/artifacts/netdata_"${VERSION}"_*.deb || exit 1

12 # Install testing tools

@@ -21,7 +21,7 @@ install_fedora_like() {

22 pkg_version="$(echo "${VERSION}" | tr - .)"

24 - # Install NetData

24 + # Install Netdata

25 "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm

27 # Install testing tools

@@ -39,7 +39,7 @@ install_centos() {

39 # Install EPEL (needed for `jq`

40 "$PKGMGR" install -y epel-release || exit 1

42 - # Install NetData

42 + # Install Netdata

43 "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm

45 # Install testing tools

@@ -52,7 +52,7 @@ install_suse_like() {

53 pkg_version="$(echo "${VERSION}" | tr - .)"

55 - # Install NetData

55 + # Install Netdata

56 zypper install -y --allow-unsigned-rpm /netdata/artifacts/netdata-"${pkg_version}"-*.rpm

58 # Install testing tools

backends/WALKTHROUGH.md

+6 -6

@@ -176,14 +176,14 @@ Prometheus’s homepage and begin to type ‘netdata\_’ Prometheus should auto

176

177 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)

178

179 -Let’s now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a

179 +Let’s now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a

180 pointless busy loop. On the shell do the following:

181

182 ```sh

183 [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done

184 ```

185

186 -Our NetData cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s

186 +Our Netdata cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s

187 keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes> We are

188 setting out to graph the data in the CPU chart so let’s search for “system.cpu”in the metrics page above. We come across

189 a section of metrics with the first comments `# COMMENT homogeneous chart "system.cpu", context "system.cpu", family

@@ -209,18 +209,18 @@ query the dimension also. Place this into our query text box.

209

210 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)

211

212 -Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from NetData by using

212 +Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from Netdata by using

213 the `chart` dimension. If you’d like you can combine the ‘chart’ and ‘instance’ dimension to create per-instance charts.

214 Let’s give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`

215

216 -This is the basics of using Prometheus to query NetData. I’d advise everyone at this point to read [this

217 -page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from

216 +This is the basics of using Prometheus to query Netdata. I’d advise everyone at this point to read [this

217 +page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from

218 its internal DB or can send metrics “as-collected” by specifying the ‘source=as-collected’ url parameter like so.

219 <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use

220 this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to

221 obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the

222 `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the

223 -metrics returned by NetData's internal database (not specifying any source= url parameter) then use that. If you find

223 +metrics returned by Netdata's internal database (not specifying any source= url parameter) then use that. If you find

224 limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired

225 chart.

226

backends/prometheus/README.md

+1 -1

@@ -125,7 +125,7 @@ scrape_configs:

125

126 #### Install nodes.yml

127

128 -The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the

128 +The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the

129 values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and

130 add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.

131

build_external/scenarios/aclk-testing/agent_netdata.conf

+28 -28

@@ -1124,7 +1124,7 @@

1124 # context = netdata.statsd_cpu

1125 # priority = 132001

1126 # name = netdata.plugin_statsd_charting_cpu

1127 - # title = NetData statsd charting thread CPU usage

1127 + # title = Netdata statsd charting thread CPU usage

1128 # dim user name = user

1129 # dim user algorithm = incremental

1130 # dim user multiplier = 1

@@ -1145,7 +1145,7 @@

1145 # context = netdata.statsd_cpu

1146 # priority = 132002

1147 # name = netdata.plugin_statsd_collector1_cpu

1148 - # title = NetData statsd collector thread No 1 CPU usage

1148 + # title = Netdata statsd collector thread No 1 CPU usage

1149 # dim user name = user

1150 # dim user algorithm = incremental

1151 # dim user multiplier = 1

@@ -1955,7 +1955,7 @@

1955 # context = netdata.plugin_cgroups_cpu

1956 # priority = 132000

1957 # name = netdata.plugin_cgroups_cpu

1958 - # title = NetData CGroups Plugin CPU usage

1958 + # title = Netdata CGroups Plugin CPU usage

1959 # dim user name = user

1960 # dim user algorithm = incremental

1961 # dim user multiplier = 1

@@ -1976,7 +1976,7 @@

1976 # context = netdata.plugin_diskspace

1977 # priority = 132020

1978 # name = netdata.plugin_diskspace

1979 - # title = NetData Disk Space Plugin CPU usage

1979 + # title = Netdata Disk Space Plugin CPU usage

1980 # dim user name = user

1981 # dim user algorithm = incremental

1982 # dim user multiplier = 1

@@ -1997,7 +1997,7 @@

1997 # context = netdata.plugin_diskspace_dt

1998 # priority = 132021

1999 # name = netdata.plugin_diskspace_dt

2000 - # title = NetData Disk Space Plugin Duration

2000 + # title = Netdata Disk Space Plugin Duration

2001 # dim duration name = duration

2002 # dim duration algorithm = absolute

2003 # dim duration multiplier = 1

@@ -4844,7 +4844,7 @@

4844 # context = netdata.plugin_proc_modules

4845 # priority = 132001

4846 # name = netdata.plugin_proc_modules

4847 - # title = NetData Proc Plugin Modules Durations

4847 + # title = Netdata Proc Plugin Modules Durations

4848 # dim stat name = stat

4849 # dim stat algorithm = absolute

4850 # dim stat multiplier = 1

@@ -4949,7 +4949,7 @@

4949 # context = netdata.plugin_proc_cpu

4950 # priority = 132000

4951 # name = netdata.plugin_proc_cpu

4952 - # title = NetData Proc Plugin CPU usage

4952 + # title = Netdata Proc Plugin CPU usage

4953 # dim user name = user

4954 # dim user algorithm = incremental

4955 # dim user multiplier = 1

@@ -4970,7 +4970,7 @@

4970 # context = netdata.server_cpu

4971 # priority = 130000

4972 # name = netdata.server_cpu

4973 - # title = NetData CPU usage

4973 + # title = Netdata CPU usage

4974 # dim user name = user

4975 # dim user algorithm = incremental

4976 # dim user multiplier = 1

@@ -4991,7 +4991,7 @@

4991 # context = netdata.clients

4992 # priority = 130200

4993 # name = netdata.clients

4994 - # title = NetData Web Clients

4994 + # title = Netdata Web Clients

4995 # dim clients name = clients

4996 # dim clients algorithm = absolute

4997 # dim clients multiplier = 1

@@ -5008,7 +5008,7 @@

5008 # context = netdata.requests

5009 # priority = 130300

5010 # name = netdata.requests

5011 - # title = NetData Web Requests

5011 + # title = Netdata Web Requests

5012 # dim requests name = requests

5013 # dim requests algorithm = incremental

5014 # dim requests multiplier = 1

@@ -5025,7 +5025,7 @@

5025 # context = netdata.net

5026 # priority = 130000

5027 # name = netdata.net

5028 - # title = NetData Network Traffic

5028 + # title = Netdata Network Traffic

5029 # dim in name = in

5030 # dim in algorithm = incremental

5031 # dim in multiplier = 8

@@ -5046,7 +5046,7 @@

5046 # context = netdata.response_time

5047 # priority = 130400

5048 # name = netdata.response_time

5049 - # title = NetData API Response Time

5049 + # title = Netdata API Response Time

5050 # dim average name = average

5051 # dim average algorithm = absolute

5052 # dim average multiplier = 1

@@ -5067,7 +5067,7 @@

5067 # context = netdata.compression_ratio

5068 # priority = 130500

5069 # name = netdata.compression_ratio

5070 - # title = NetData API Responses Compression Savings Ratio

5070 + # title = Netdata API Responses Compression Savings Ratio

5071 # dim savings name = savings

5072 # dim savings algorithm = absolute

5073 # dim savings multiplier = 1

@@ -5084,7 +5084,7 @@

5084 # context = netdata.dbengine_compression_ratio

5085 # priority = 130502

5086 # name = netdata.dbengine_compression_ratio

5087 - # title = NetData DB engine data extents' compression savings ratio

5087 + # title = Netdata DB engine data extents' compression savings ratio

5088 # dim savings name = savings

5089 # dim savings algorithm = absolute

5090 # dim savings multiplier = 1

@@ -5101,7 +5101,7 @@

5101 # context = netdata.page_cache_hit_ratio

5102 # priority = 130503

5103 # name = netdata.page_cache_hit_ratio

5104 - # title = NetData DB engine page cache hit ratio

5104 + # title = Netdata DB engine page cache hit ratio

5105 # dim ratio name = ratio

5106 # dim ratio algorithm = absolute

5107 # dim ratio multiplier = 1

@@ -5118,7 +5118,7 @@

5118 # context = netdata.page_cache_stats

5119 # priority = 130504

5120 # name = netdata.page_cache_stats

5121 - # title = NetData dbengine page cache statistics

5121 + # title = Netdata dbengine page cache statistics

5122 # dim descriptors name = descriptors

5123 # dim descriptors algorithm = absolute

5124 # dim descriptors multiplier = 1

@@ -5155,7 +5155,7 @@

5155 # context = netdata.dbengine_long_term_page_stats

5156 # priority = 130505

5157 # name = netdata.dbengine_long_term_page_stats

5158 - # title = NetData dbengine long-term page statistics

5158 + # title = Netdata dbengine long-term page statistics

5159 # dim total name = total

5160 # dim total algorithm = absolute

5161 # dim total multiplier = 1

@@ -5184,7 +5184,7 @@

5184 # context = netdata.dbengine_io_throughput

5185 # priority = 130506

5186 # name = netdata.dbengine_io_throughput

5187 - # title = NetData DB engine I/O throughput

5187 + # title = Netdata DB engine I/O throughput

5188 # dim reads name = reads

5189 # dim reads algorithm = incremental

5190 # dim reads multiplier = 1

@@ -5205,7 +5205,7 @@

5205 # context = netdata.dbengine_io_operations

5206 # priority = 130507

5207 # name = netdata.dbengine_io_operations

5208 - # title = NetData DB engine I/O operations

5208 + # title = Netdata DB engine I/O operations

5209 # dim reads name = reads

5210 # dim reads algorithm = incremental

5211 # dim reads multiplier = 1

@@ -5226,7 +5226,7 @@

5226 # context = netdata.dbengine_global_errors

5227 # priority = 130508

5228 # name = netdata.dbengine_global_errors

5229 - # title = NetData DB engine errors

5229 + # title = Netdata DB engine errors

5230 # dim io_errors name = io_errors

5231 # dim io_errors algorithm = incremental

5232 # dim io_errors multiplier = 1

@@ -5251,7 +5251,7 @@

5251 # context = netdata.dbengine_global_file_descriptors

5252 # priority = 130509

5253 # name = netdata.dbengine_global_file_descriptors

5254 - # title = NetData DB engine File Descriptors

5254 + # title = Netdata DB engine File Descriptors

5255 # dim current name = current

5256 # dim current algorithm = absolute

5257 # dim current multiplier = 1

@@ -5272,7 +5272,7 @@

5272 # context = netdata.dbengine_ram

5273 # priority = 130510

5274 # name = netdata.dbengine_ram

5275 - # title = NetData DB engine RAM usage

5275 + # title = Netdata DB engine RAM usage

5276 # dim cache name = cache

5277 # dim cache algorithm = absolute

5278 # dim cache multiplier = 1

@@ -5297,7 +5297,7 @@

5297 # context = netdata.web_cpu

5298 # priority = 132003

5299 # name = netdata.web_thread4_cpu

5300 - # title = NetData web server thread No 4 CPU usage

5300 + # title = Netdata web server thread No 4 CPU usage

5301 # dim user name = user

5302 # dim user algorithm = incremental

5303 # dim user multiplier = 1

@@ -5318,7 +5318,7 @@

5318 # context = netdata.web_cpu

5319 # priority = 132000

5320 # name = netdata.web_thread1_cpu

5321 - # title = NetData web server thread No 1 CPU usage

5321 + # title = Netdata web server thread No 1 CPU usage

5322 # dim user name = user

5323 # dim user algorithm = incremental

5324 # dim user multiplier = 1

@@ -5339,7 +5339,7 @@

5339 # context = netdata.web_cpu

5340 # priority = 132005

5341 # name = netdata.web_thread6_cpu

5342 - # title = NetData web server thread No 6 CPU usage

5342 + # title = Netdata web server thread No 6 CPU usage

5343 # dim user name = user

5344 # dim user algorithm = incremental

5345 # dim user multiplier = 1

@@ -5360,7 +5360,7 @@

5360 # context = netdata.web_cpu

5361 # priority = 132002

5362 # name = netdata.web_thread3_cpu

5363 - # title = NetData web server thread No 3 CPU usage

5363 + # title = Netdata web server thread No 3 CPU usage

5364 # dim user name = user

5365 # dim user algorithm = incremental

5366 # dim user multiplier = 1

@@ -5381,7 +5381,7 @@

5381 # context = netdata.web_cpu

5382 # priority = 132001

5383 # name = netdata.web_thread2_cpu

5384 - # title = NetData web server thread No 2 CPU usage

5384 + # title = Netdata web server thread No 2 CPU usage

5385 # dim user name = user

5386 # dim user algorithm = incremental

5387 # dim user multiplier = 1

@@ -5520,7 +5520,7 @@

5520 # context = netdata.web_cpu

5521 # priority = 132004

5522 # name = netdata.web_thread5_cpu

5523 - # title = NetData web server thread No 5 CPU usage

5523 + # title = Netdata web server thread No 5 CPU usage

5524 # dim user name = user

5525 # dim user algorithm = incremental

5526 # dim user multiplier = 1

collectors/statsd.plugin/statsd.c

+1 -1

@@ -2441,7 +2441,7 @@ void *statsd_main(void *ptr) {

2441 char title[100 + 1];

2442

2443 snprintfz(id, 100, "plugin_statsd_collector%d_cpu", i + 1);

2444 - snprintfz(title, 100, "NetData statsd collector thread No %d CPU usage", i + 1);

2444 + snprintfz(title, 100, "Netdata statsd collector thread No %d CPU usage", i + 1);

2445

2446 statsd.collection_threads_status[i].st_cpu = rrdset_create_localhost(

2447 "netdata"

exporting/WALKTHROUGH.md

+6 -6

@@ -178,14 +178,14 @@ Prometheus's homepage and begin to type `netdata\_` Prometheus should auto compl

178

179 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)

180

181 -Let's now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a

181 +Let's now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a

182 pointless busy loop. On the shell do the following:

183

184 ```sh

185 [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done

186 ```

187

188 -Our NetData cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's

188 +Our Netdata cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's

189 keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes>. We are

190 setting out to graph the data in the CPU chart so let's search for `system.cpu` in the metrics page above. We come

191 across a section of metrics with the first comments `# COMMENT homogeneous chart "system.cpu", context "system.cpu",

@@ -211,18 +211,18 @@ query the dimension also. Place this into our query text box.

211

212 ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)

213

214 -Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from NetData by using

214 +Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from Netdata by using

215 the `chart` dimension. If you'd like you can combine the `chart` and `instance` dimension to create per-instance charts.

216 Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`

217

218 -This is the basics of using Prometheus to query NetData. I'd advise everyone at this point to read [this

219 -page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from

218 +This is the basics of using Prometheus to query Netdata. I'd advise everyone at this point to read [this

219 +page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from

220 its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so.

221 <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use

222 this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to

223 obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the

224 `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the

225 -metrics returned by NetData's internal database (not specifying any source= URL parameter) then use that. If you find

225 +metrics returned by Netdata's internal database (not specifying any source= URL parameter) then use that. If you find

226 limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired

227 chart.

228

exporting/prometheus/README.md

+1 -1

@@ -128,7 +128,7 @@ scrape_configs:

128

129 #### Install nodes.yml

130

131 -The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the

131 +The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the

132 values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and

133 add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.

134

health/notifications/alarm-notify.sh.in

+2 -2

@@ -2137,12 +2137,12 @@ send_dynatrace() {

2137 [ "${SEND_DYNATRACE}" != "YES" ] && return 1

2138

2139 local dynatrace_url="${DYNATRACE_SERVER}/e/${DYNATRACE_SPACE}/api/v1/events"

2140 - local description="NetData Notification for: ${host} ${chart}.${name} is ${status}"

2140 + local description="Netdata Notification for: ${host} ${chart}.${name} is ${status}"

2141 local payload=""

2142

2143 payload=$(cat <<EOF

2144 {

2145 - "title": "NetData Alarm from ${host}",

2145 + "title": "Netdata Alarm from ${host}",

2146 "source" : "${DYNATRACE_ANNOTATION_TYPE}",

2147 "description" : "${description}",

2148 "eventType": "${DYNATRACE_EVENT}",

health/notifications/health_alarm_notify.conf

+2 -2

@@ -253,13 +253,13 @@ DYNATRACE_TOKEN=""

253 DYNATRACE_SPACE=""

254

255 # Generate a Server Tag. On the Dynatrace Server go to Settings --> Tags --> Manually applied tags create the Tag

256 -# The NetData alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag

256 +# The Netdata alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag

257 # you created.

258 # Required

259 DYNATRACE_TAG_VALUE=""

260

261 # Change this to what you want

262 -DYNATRACE_ANNOTATION_TYPE="NetData Alarm"

262 +DYNATRACE_ANNOTATION_TYPE="Netdata Alarm"

263

264 # This can be CUSTOM_INFO, CUSTOM_ANNOTATION, CUSTOM_CONFIGURATION, CUSTOM_DEPLOYMENT

265 # Applying default value

web/api/netdata-swagger.json

+2 -2

@@ -1,7 +1,7 @@

1 {

2 "openapi": "3.0.0",

3 "info": {

4 - "title": "NetData API",

4 + "title": "Netdata API",

5 "description": "Real-time performance and health monitoring.",

6 "version": "1.11.1_rolling"

7 },

@@ -1343,7 +1343,7 @@

1343 },

1344 "priority": {

1345 "type": "number",

1346 - "description": "The relative priority of the chart. NetData does not care about priorities. This is just an indication of importance for the chart viewers to sort charts of higher priority (lower number) closer to the top. Priority sorting should only be used among charts of the same type or family."

1346 + "description": "The relative priority of the chart. Netdata does not care about priorities. This is just an indication of importance for the chart viewers to sort charts of higher priority (lower number) closer to the top. Priority sorting should only be used among charts of the same type or family."

1347 },

1348 "enabled": {

1349 "type": "boolean",

web/api/netdata-swagger.yaml

+2 -2

@@ -1,6 +1,6 @@

1 openapi: 3.0.0

2 info:

3 - title: NetData API

3 + title: Netdata API

4 description: Real-time performance and health monitoring.

5 version: 1.11.1_rolling

6 paths:

@@ -1082,7 +1082,7 @@ components:

1082 description: The title of the chart.

1083 priority:

1084 type: number

1085 - description: The relative priority of the chart. NetData does not care about

1085 + description: The relative priority of the chart. Netdata does not care about

1086 priorities. This is just an indication of importance for the chart

1087 viewers to sort charts of higher priority (lower number) closer to

1088 the top. Priority sorting should only be used among charts of the

web/gui/dashboard/dashboard.html

+4 -4

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData Dashboard</title>

5 + <title>Netdata Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

@@ -25,7 +25,7 @@

26 <div class="container-fluid">

28 -<h1>NetData Custom Dashboard <div data-netdata="system.cpu" data-chart-library="sparkline" data-height="30" data-after="-600" data-sparkline-linecolor="#888"></div></h1>

28 +<h1>Netdata Custom Dashboard <div data-netdata="system.cpu" data-chart-library="sparkline" data-height="30" data-after="-600" data-sparkline-linecolor="#888"></div></h1>

30 This is a template for building custom dashboards. To build a dashboard you just do this:

@@ -518,8 +518,8 @@ Sparklines using dygraphs

518

519 <hr>

520 <h1>Google Charts</h1>

521 -NetData was originaly developed with Google Charts.

522 -NetData is a complete Google Visualization API provider.

521 +Netdata was originaly developed with Google Charts.

522 +Netdata is a complete Google Visualization API provider.

523 <br/>

524 <div style="width: 33%; display: inline-block;">

525 <div data-netdata="system.processes"

web/gui/dashboard/demo.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData Dashboard</title>

5 + <title>Netdata Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/gui/dashboard/demo2.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData Dashboard</title>

5 + <title>Netdata Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/gui/dashboard/demosites.html

+1 -1

@@ -4,7 +4,7 @@

4 <head>

5 <meta http-equiv="Refresh" content="0; url=https://www.netdata.cloud">

6 <meta charset=utf-8>

7 - <title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title>

7 + <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>

8 <meta name=author content="Costa Tsaousis">

9 <meta name=description content="Unparalleled insights, in real-time, of everything happening on your Linux systems and applications, with stunning, interactive web dashboards and powerful performance and health alarms.">

web/gui/dashboard/demosites2.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData - Real-time performance monitoring, done right!</title>

5 + <title>Netdata - Real-time performance monitoring, done right!</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/gui/dashboard/index-node-view.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData TV Dashboard</title>

5 + <title>Netdata TV Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/gui/dashboard/infographic.html

+1 -1

@@ -3,7 +3,7 @@

3 <html lang=en-us>

4 <head>

5 <meta charset=utf-8>

6 - <title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title>

6 + <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>

7 <meta name=author content="Costa Tsaousis">

8 <meta name=description content="Unparalleled insights, in real-time, of everything happening on your Linux systems and applications, with stunning, interactive web dashboards and powerful performance and health alarms.">

web/gui/dashboard/tv-react.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData TV Dashboard</title>

5 + <title>Netdata TV Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/gui/dashboard/tv.html

+1 -1

@@ -2,7 +2,7 @@

2

3 <html lang="en">

4 <head>

5 - <title>NetData TV Dashboard</title>

5 + <title>Netdata TV Dashboard</title>

6 <meta name="application-name" content="netdata">

8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

web/server/web_client.c

+1 -1

@@ -1177,7 +1177,7 @@ void web_client_build_http_header(struct web_client *w) {

1177 buffer_sprintf(w->response.header_output,

1178 "HTTP/1.1 %d %s\r\n"

1179 "Connection: %s\r\n"

1180 - "Server: NetData Embedded HTTP Server %s\r\n"

1180 + "Server: Netdata Embedded HTTP Server %s\r\n"

1181 "Access-Control-Allow-Origin: %s\r\n"

1182 "Access-Control-Allow-Credentials: true\r\n"

1183 "Content-Type: %s\r\n"