archive/netdata_netdata
0
0
Fork 0
mirror of https://github.com/netdata/netdata.git synced 2025-04-26 13:54:48 +00:00
Code Issues Projects Releases Wiki Activity

Clean netdata naming ()

Browse source 
* replace "NetData" with "Netdata"

* replace "NetData" with "Netdata"
This commit is contained in:
Andrew Maguire 2021-09-04 16:47:16 +01:00 • committed by GitHub
parent 37d249544c
commit 9f8dc123a2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
21 changed files with 68 additions and 68 deletions

8
.github/scripts/pkg-test.sh vendored
View file

@ -6,7 +6,7 @@ install_debian_like() {
apt-get update apt-get update
# Install NetData # Install Netdata
apt-get install -y /netdata/artifacts/netdata_"${VERSION}"_*.deb || exit 1 apt-get install -y /netdata/artifacts/netdata_"${VERSION}"_*.deb || exit 1
# Install testing tools # Install testing tools
@ -21,7 +21,7 @@ install_fedora_like() {
pkg_version="$(echo "${VERSION}" | tr - .)" pkg_version="$(echo "${VERSION}" | tr - .)"
# Install NetData # Install Netdata
"$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
# Install testing tools # Install testing tools
@ -39,7 +39,7 @@ install_centos() {
# Install EPEL (needed for `jq` # Install EPEL (needed for `jq`
"$PKGMGR" install -y epel-release || exit 1 "$PKGMGR" install -y epel-release || exit 1
# Install NetData # Install Netdata
"$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm "$PKGMGR" install -y /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
# Install testing tools # Install testing tools
@ -52,7 +52,7 @@ install_suse_like() {
pkg_version="$(echo "${VERSION}" | tr - .)" pkg_version="$(echo "${VERSION}" | tr - .)"
# Install NetData # Install Netdata
zypper install -y --allow-unsigned-rpm /netdata/artifacts/netdata-"${pkg_version}"-*.rpm zypper install -y --allow-unsigned-rpm /netdata/artifacts/netdata-"${pkg_version}"-*.rpm
# Install testing tools # Install testing tools

12
backends/WALKTHROUGH.md
View file

@ -176,14 +176,14 @@ Prometheus’s homepage and begin to type ‘netdata\_’ Prometheus should auto
![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png) ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)
Let’s now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a Let’s now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a
pointless busy loop. On the shell do the following: pointless busy loop. On the shell do the following:
```sh ```sh
[root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done
``` ```
Our NetData cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s Our Netdata cpu graph should be showing some activity. Let’s represent this in Prometheus. In order to do this let’s
keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes> We are keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes> We are
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 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
a section of metrics with the first comments `# COMMENT homogeneous chart "system.cpu", context "system.cpu", family 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.
![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png) ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)
Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from NetData by using Awesome, this is exactly what we wanted. If you haven’t caught on yet we can emulate entire charts from Netdata by using
the `chart` dimension. If you’d like you can combine the ‘chart’ and ‘instance’ dimension to create per-instance charts. the `chart` dimension. If you’d like you can combine the ‘chart’ and ‘instance’ dimension to create per-instance charts.
Let’s give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}` Let’s give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
This is the basics of using Prometheus to query NetData. I’d advise everyone at this point to read [this This is the basics of using Prometheus to query Netdata. I’d advise everyone at this point to read [this
page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from page](../backends/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
its internal DB or can send metrics “as-collected” by specifying the ‘source=as-collected’ url parameter like so. its internal DB or can send metrics “as-collected” by specifying the ‘source=as-collected’ url parameter like so.
<http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the
`irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the
metrics returned by NetData's internal database (not specifying any source= url parameter) then use that. If you find metrics returned by Netdata's internal database (not specifying any source= url parameter) then use that. If you find
limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired
chart. chart.

2
backends/prometheus/README.md
View file

@ -125,7 +125,7 @@ scrape_configs:
#### Install nodes.yml #### Install nodes.yml
The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the
values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and
add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above. add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.

56
build_external/scenarios/aclk-testing/agent_netdata.conf
View file

@ -1124,7 +1124,7 @@
# context = netdata.statsd_cpu # context = netdata.statsd_cpu
# priority = 132001 # priority = 132001
# name = netdata.plugin_statsd_charting_cpu # name = netdata.plugin_statsd_charting_cpu
# title = NetData statsd charting thread CPU usage # title = Netdata statsd charting thread CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -1145,7 +1145,7 @@
# context = netdata.statsd_cpu # context = netdata.statsd_cpu
# priority = 132002 # priority = 132002
# name = netdata.plugin_statsd_collector1_cpu # name = netdata.plugin_statsd_collector1_cpu
# title = NetData statsd collector thread No 1 CPU usage # title = Netdata statsd collector thread No 1 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -1955,7 +1955,7 @@
# context = netdata.plugin_cgroups_cpu # context = netdata.plugin_cgroups_cpu
# priority = 132000 # priority = 132000
# name = netdata.plugin_cgroups_cpu # name = netdata.plugin_cgroups_cpu
# title = NetData CGroups Plugin CPU usage # title = Netdata CGroups Plugin CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -1976,7 +1976,7 @@
# context = netdata.plugin_diskspace # context = netdata.plugin_diskspace
# priority = 132020 # priority = 132020
# name = netdata.plugin_diskspace # name = netdata.plugin_diskspace
# title = NetData Disk Space Plugin CPU usage # title = Netdata Disk Space Plugin CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -1997,7 +1997,7 @@
# context = netdata.plugin_diskspace_dt # context = netdata.plugin_diskspace_dt
# priority = 132021 # priority = 132021
# name = netdata.plugin_diskspace_dt # name = netdata.plugin_diskspace_dt
# title = NetData Disk Space Plugin Duration # title = Netdata Disk Space Plugin Duration
# dim duration name = duration # dim duration name = duration
# dim duration algorithm = absolute # dim duration algorithm = absolute
# dim duration multiplier = 1 # dim duration multiplier = 1
@ -4844,7 +4844,7 @@
# context = netdata.plugin_proc_modules # context = netdata.plugin_proc_modules
# priority = 132001 # priority = 132001
# name = netdata.plugin_proc_modules # name = netdata.plugin_proc_modules
# title = NetData Proc Plugin Modules Durations # title = Netdata Proc Plugin Modules Durations
# dim stat name = stat # dim stat name = stat
# dim stat algorithm = absolute # dim stat algorithm = absolute
# dim stat multiplier = 1 # dim stat multiplier = 1
@ -4949,7 +4949,7 @@
# context = netdata.plugin_proc_cpu # context = netdata.plugin_proc_cpu
# priority = 132000 # priority = 132000
# name = netdata.plugin_proc_cpu # name = netdata.plugin_proc_cpu
# title = NetData Proc Plugin CPU usage # title = Netdata Proc Plugin CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -4970,7 +4970,7 @@
# context = netdata.server_cpu # context = netdata.server_cpu
# priority = 130000 # priority = 130000
# name = netdata.server_cpu # name = netdata.server_cpu
# title = NetData CPU usage # title = Netdata CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -4991,7 +4991,7 @@
# context = netdata.clients # context = netdata.clients
# priority = 130200 # priority = 130200
# name = netdata.clients # name = netdata.clients
# title = NetData Web Clients # title = Netdata Web Clients
# dim clients name = clients # dim clients name = clients
# dim clients algorithm = absolute # dim clients algorithm = absolute
# dim clients multiplier = 1 # dim clients multiplier = 1
@ -5008,7 +5008,7 @@
# context = netdata.requests # context = netdata.requests
# priority = 130300 # priority = 130300
# name = netdata.requests # name = netdata.requests
# title = NetData Web Requests # title = Netdata Web Requests
# dim requests name = requests # dim requests name = requests
# dim requests algorithm = incremental # dim requests algorithm = incremental
# dim requests multiplier = 1 # dim requests multiplier = 1
@ -5025,7 +5025,7 @@
# context = netdata.net # context = netdata.net
# priority = 130000 # priority = 130000
# name = netdata.net # name = netdata.net
# title = NetData Network Traffic # title = Netdata Network Traffic
# dim in name = in # dim in name = in
# dim in algorithm = incremental # dim in algorithm = incremental
# dim in multiplier = 8 # dim in multiplier = 8
@ -5046,7 +5046,7 @@
# context = netdata.response_time # context = netdata.response_time
# priority = 130400 # priority = 130400
# name = netdata.response_time # name = netdata.response_time
# title = NetData API Response Time # title = Netdata API Response Time
# dim average name = average # dim average name = average
# dim average algorithm = absolute # dim average algorithm = absolute
# dim average multiplier = 1 # dim average multiplier = 1
@ -5067,7 +5067,7 @@
# context = netdata.compression_ratio # context = netdata.compression_ratio
# priority = 130500 # priority = 130500
# name = netdata.compression_ratio # name = netdata.compression_ratio
# title = NetData API Responses Compression Savings Ratio # title = Netdata API Responses Compression Savings Ratio
# dim savings name = savings # dim savings name = savings
# dim savings algorithm = absolute # dim savings algorithm = absolute
# dim savings multiplier = 1 # dim savings multiplier = 1
@ -5084,7 +5084,7 @@
# context = netdata.dbengine_compression_ratio # context = netdata.dbengine_compression_ratio
# priority = 130502 # priority = 130502
# name = netdata.dbengine_compression_ratio # name = netdata.dbengine_compression_ratio
# title = NetData DB engine data extents' compression savings ratio # title = Netdata DB engine data extents' compression savings ratio
# dim savings name = savings # dim savings name = savings
# dim savings algorithm = absolute # dim savings algorithm = absolute
# dim savings multiplier = 1 # dim savings multiplier = 1
@ -5101,7 +5101,7 @@
# context = netdata.page_cache_hit_ratio # context = netdata.page_cache_hit_ratio
# priority = 130503 # priority = 130503
# name = netdata.page_cache_hit_ratio # name = netdata.page_cache_hit_ratio
# title = NetData DB engine page cache hit ratio # title = Netdata DB engine page cache hit ratio
# dim ratio name = ratio # dim ratio name = ratio
# dim ratio algorithm = absolute # dim ratio algorithm = absolute
# dim ratio multiplier = 1 # dim ratio multiplier = 1
@ -5118,7 +5118,7 @@
# context = netdata.page_cache_stats # context = netdata.page_cache_stats
# priority = 130504 # priority = 130504
# name = netdata.page_cache_stats # name = netdata.page_cache_stats
# title = NetData dbengine page cache statistics # title = Netdata dbengine page cache statistics
# dim descriptors name = descriptors # dim descriptors name = descriptors
# dim descriptors algorithm = absolute # dim descriptors algorithm = absolute
# dim descriptors multiplier = 1 # dim descriptors multiplier = 1
@ -5155,7 +5155,7 @@
# context = netdata.dbengine_long_term_page_stats # context = netdata.dbengine_long_term_page_stats
# priority = 130505 # priority = 130505
# name = netdata.dbengine_long_term_page_stats # name = netdata.dbengine_long_term_page_stats
# title = NetData dbengine long-term page statistics # title = Netdata dbengine long-term page statistics
# dim total name = total # dim total name = total
# dim total algorithm = absolute # dim total algorithm = absolute
# dim total multiplier = 1 # dim total multiplier = 1
@ -5184,7 +5184,7 @@
# context = netdata.dbengine_io_throughput # context = netdata.dbengine_io_throughput
# priority = 130506 # priority = 130506
# name = netdata.dbengine_io_throughput # name = netdata.dbengine_io_throughput
# title = NetData DB engine I/O throughput # title = Netdata DB engine I/O throughput
# dim reads name = reads # dim reads name = reads
# dim reads algorithm = incremental # dim reads algorithm = incremental
# dim reads multiplier = 1 # dim reads multiplier = 1
@ -5205,7 +5205,7 @@
# context = netdata.dbengine_io_operations # context = netdata.dbengine_io_operations
# priority = 130507 # priority = 130507
# name = netdata.dbengine_io_operations # name = netdata.dbengine_io_operations
# title = NetData DB engine I/O operations # title = Netdata DB engine I/O operations
# dim reads name = reads # dim reads name = reads
# dim reads algorithm = incremental # dim reads algorithm = incremental
# dim reads multiplier = 1 # dim reads multiplier = 1
@ -5226,7 +5226,7 @@
# context = netdata.dbengine_global_errors # context = netdata.dbengine_global_errors
# priority = 130508 # priority = 130508
# name = netdata.dbengine_global_errors # name = netdata.dbengine_global_errors
# title = NetData DB engine errors # title = Netdata DB engine errors
# dim io_errors name = io_errors # dim io_errors name = io_errors
# dim io_errors algorithm = incremental # dim io_errors algorithm = incremental
# dim io_errors multiplier = 1 # dim io_errors multiplier = 1
@ -5251,7 +5251,7 @@
# context = netdata.dbengine_global_file_descriptors # context = netdata.dbengine_global_file_descriptors
# priority = 130509 # priority = 130509
# name = netdata.dbengine_global_file_descriptors # name = netdata.dbengine_global_file_descriptors
# title = NetData DB engine File Descriptors # title = Netdata DB engine File Descriptors
# dim current name = current # dim current name = current
# dim current algorithm = absolute # dim current algorithm = absolute
# dim current multiplier = 1 # dim current multiplier = 1
@ -5272,7 +5272,7 @@
# context = netdata.dbengine_ram # context = netdata.dbengine_ram
# priority = 130510 # priority = 130510
# name = netdata.dbengine_ram # name = netdata.dbengine_ram
# title = NetData DB engine RAM usage # title = Netdata DB engine RAM usage
# dim cache name = cache # dim cache name = cache
# dim cache algorithm = absolute # dim cache algorithm = absolute
# dim cache multiplier = 1 # dim cache multiplier = 1
@ -5297,7 +5297,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132003 # priority = 132003
# name = netdata.web_thread4_cpu # name = netdata.web_thread4_cpu
# title = NetData web server thread No 4 CPU usage # title = Netdata web server thread No 4 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -5318,7 +5318,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132000 # priority = 132000
# name = netdata.web_thread1_cpu # name = netdata.web_thread1_cpu
# title = NetData web server thread No 1 CPU usage # title = Netdata web server thread No 1 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -5339,7 +5339,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132005 # priority = 132005
# name = netdata.web_thread6_cpu # name = netdata.web_thread6_cpu
# title = NetData web server thread No 6 CPU usage # title = Netdata web server thread No 6 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -5360,7 +5360,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132002 # priority = 132002
# name = netdata.web_thread3_cpu # name = netdata.web_thread3_cpu
# title = NetData web server thread No 3 CPU usage # title = Netdata web server thread No 3 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -5381,7 +5381,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132001 # priority = 132001
# name = netdata.web_thread2_cpu # name = netdata.web_thread2_cpu
# title = NetData web server thread No 2 CPU usage # title = Netdata web server thread No 2 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1
@ -5520,7 +5520,7 @@
# context = netdata.web_cpu # context = netdata.web_cpu
# priority = 132004 # priority = 132004
# name = netdata.web_thread5_cpu # name = netdata.web_thread5_cpu
# title = NetData web server thread No 5 CPU usage # title = Netdata web server thread No 5 CPU usage
# dim user name = user # dim user name = user
# dim user algorithm = incremental # dim user algorithm = incremental
# dim user multiplier = 1 # dim user multiplier = 1

2
collectors/statsd.plugin/statsd.c
View file

@ -2441,7 +2441,7 @@ void *statsd_main(void *ptr) {
char title[100 + 1]; char title[100 + 1];
snprintfz(id, 100, "plugin_statsd_collector%d_cpu", i + 1); snprintfz(id, 100, "plugin_statsd_collector%d_cpu", i + 1);
snprintfz(title, 100, "NetData statsd collector thread No %d CPU usage", i + 1); snprintfz(title, 100, "Netdata statsd collector thread No %d CPU usage", i + 1);
statsd.collection_threads_status[i].st_cpu = rrdset_create_localhost( statsd.collection_threads_status[i].st_cpu = rrdset_create_localhost(
"netdata" "netdata"

12
exporting/WALKTHROUGH.md
View file

@ -178,14 +178,14 @@ Prometheus's homepage and begin to type `netdata\_` Prometheus should auto compl
![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png) ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.13.43%20PM.png)
Let's now start exploring how we can graph some metrics. Back in our NetData container lets get the CPU spinning with a Let's now start exploring how we can graph some metrics. Back in our Netdata container lets get the CPU spinning with a
pointless busy loop. On the shell do the following: pointless busy loop. On the shell do the following:
```sh ```sh
[root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done [root@netdata /]# while true; do echo "HOT HOT HOT CPU"; done
``` ```
Our NetData cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's Our Netdata cpu graph should be showing some activity. Let's represent this in Prometheus. In order to do this let's
keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes>. We are keep our metrics page open for reference: <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes>. We are
setting out to graph the data in the CPU chart so let's search for `system.cpu` in the metrics page above. We come 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 a section of metrics with the first comments `# COMMENT homogeneous chart "system.cpu", context "system.cpu", 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.
![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png) ![](https://github.com/ldelossa/NetdataTutorial/raw/master/Screen%20Shot%202017-07-28%20at%205.54.40%20PM.png)
Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from NetData by using Awesome, this is exactly what we wanted. If you haven't caught on yet we can emulate entire charts from Netdata by using
the `chart` dimension. If you'd like you can combine the `chart` and `instance` dimension to create per-instance charts. the `chart` dimension. If you'd like you can combine the `chart` and `instance` dimension to create per-instance charts.
Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}` Let's give this a try: `netdata_system_cpu_percentage_average{chart="system.cpu", instance="netdata:19999"}`
This is the basics of using Prometheus to query NetData. I'd advise everyone at this point to read [this This is the basics of using Prometheus to query Netdata. I'd advise everyone at this point to read [this
page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that NetData can export metrics from page](/exporting/prometheus/#using-netdata-with-prometheus). The key point here is that Netdata can export metrics from
its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so. its internal DB or can send metrics _as-collected_ by specifying the `source=as-collected` URL parameter like so.
<http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use <http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&source=as-collected> If you choose to use
this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to this method you will need to use Prometheus's set of functions here: <https://prometheus.io/docs/querying/functions/> to
obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the obtain useful metrics as you are now dealing with raw counters from the system. For example you will have to use the
`irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the `irate()` function over a counter to get that metric's rate per second. If your graphing needs are met by using the
metrics returned by NetData's internal database (not specifying any source= URL parameter) then use that. If you find metrics returned by Netdata's internal database (not specifying any source= URL parameter) then use that. If you find
limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired limitations then consider re-writing your queries using the raw data and using Prometheus functions to get the desired
chart. chart.

2
exporting/prometheus/README.md
View file

@ -128,7 +128,7 @@ scrape_configs:
#### Install nodes.yml #### Install nodes.yml
The following is completely optional, it will enable Prometheus to generate alerts from some NetData sources. Tweak the The following is completely optional, it will enable Prometheus to generate alerts from some Netdata sources. Tweak the
values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and values to your own needs. We will use the following `nodes.yml` file below. Save it at `/opt/prometheus/nodes.yml`, and
add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above. add a _- "nodes.yml"_ entry under the _rule_files:_ section in the example prometheus.yml file above.

4
health/notifications/alarm-notify.sh.in
View file

@ -2137,12 +2137,12 @@ send_dynatrace() {
[ "${SEND_DYNATRACE}" != "YES" ] && return 1 [ "${SEND_DYNATRACE}" != "YES" ] && return 1
local dynatrace_url="${DYNATRACE_SERVER}/e/${DYNATRACE_SPACE}/api/v1/events" local dynatrace_url="${DYNATRACE_SERVER}/e/${DYNATRACE_SPACE}/api/v1/events"
local description="NetData Notification for: ${host} ${chart}.${name} is ${status}" local description="Netdata Notification for: ${host} ${chart}.${name} is ${status}"
local payload="" local payload=""
payload=$(cat <<EOF payload=$(cat <<EOF
{ {
"title": "NetData Alarm from ${host}", "title": "Netdata Alarm from ${host}",
"source" : "${DYNATRACE_ANNOTATION_TYPE}", "source" : "${DYNATRACE_ANNOTATION_TYPE}",
"description" : "${description}", "description" : "${description}",
"eventType": "${DYNATRACE_EVENT}", "eventType": "${DYNATRACE_EVENT}",

4
health/notifications/health_alarm_notify.conf
View file

@ -253,13 +253,13 @@ DYNATRACE_TOKEN=""
DYNATRACE_SPACE="" DYNATRACE_SPACE=""
# Generate a Server Tag. On the Dynatrace Server go to Settings --> Tags --> Manually applied tags create the Tag # Generate a Server Tag. On the Dynatrace Server go to Settings --> Tags --> Manually applied tags create the Tag
# The NetData alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag # The Netdata alarm will be sent as a Dynatrace Event to be correlated with all those hosts tagged with this Tag
# you created. # you created.
# Required # Required
DYNATRACE_TAG_VALUE="" DYNATRACE_TAG_VALUE=""
# Change this to what you want # Change this to what you want
DYNATRACE_ANNOTATION_TYPE="NetData Alarm" DYNATRACE_ANNOTATION_TYPE="Netdata Alarm"
# This can be CUSTOM_INFO, CUSTOM_ANNOTATION, CUSTOM_CONFIGURATION, CUSTOM_DEPLOYMENT # This can be CUSTOM_INFO, CUSTOM_ANNOTATION, CUSTOM_CONFIGURATION, CUSTOM_DEPLOYMENT
# Applying default value # Applying default value

4
web/api/netdata-swagger.json
View file

@ -1,7 +1,7 @@
{ {
"openapi": "3.0.0", "openapi": "3.0.0",
"info": { "info": {
"title": "NetData API", "title": "Netdata API",
"description": "Real-time performance and health monitoring.", "description": "Real-time performance and health monitoring.",
"version": "1.11.1_rolling" "version": "1.11.1_rolling"
}, },
@ -1343,7 +1343,7 @@
}, },
"priority": { "priority": {
"type": "number", "type": "number",
"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." "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."
}, },
"enabled": { "enabled": {
"type": "boolean", "type": "boolean",

4
web/api/netdata-swagger.yaml
View file

@ -1,6 +1,6 @@
openapi: 3.0.0 openapi: 3.0.0
info: info:
title: NetData API title: Netdata API
description: Real-time performance and health monitoring. description: Real-time performance and health monitoring.
version: 1.11.1_rolling version: 1.11.1_rolling
paths: paths:
@ -1082,7 +1082,7 @@ components:
description: The title of the chart. description: The title of the chart.
priority: priority:
type: number type: number
description: The relative priority of the chart. NetData does not care about description: The relative priority of the chart. Netdata does not care about
priorities. This is just an indication of importance for the chart priorities. This is just an indication of importance for the chart
viewers to sort charts of higher priority (lower number) closer to viewers to sort charts of higher priority (lower number) closer to
the top. Priority sorting should only be used among charts of the the top. Priority sorting should only be used among charts of the

8
web/gui/dashboard/dashboard.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData Dashboard</title> <title>Netdata Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@ -25,7 +25,7 @@
<div class="container-fluid"> <div class="container-fluid">
<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> <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>
This is a template for building custom dashboards. To build a dashboard you just do this: This is a template for building custom dashboards. To build a dashboard you just do this:
@ -518,8 +518,8 @@ Sparklines using dygraphs
<hr> <hr>
<h1>Google Charts</h1> <h1>Google Charts</h1>
NetData was originaly developed with Google Charts. Netdata was originaly developed with Google Charts.
NetData is a complete Google Visualization API provider. Netdata is a complete Google Visualization API provider.
<br/> <br/>
<div style="width: 33%; display: inline-block;"> <div style="width: 33%; display: inline-block;">
<div data-netdata="system.processes" <div data-netdata="system.processes"

2
web/gui/dashboard/demo.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData Dashboard</title> <title>Netdata Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/gui/dashboard/demo2.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData Dashboard</title> <title>Netdata Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/gui/dashboard/demosites.html
View file

@ -4,7 +4,7 @@
<head> <head>
<meta http-equiv="Refresh" content="0; url=https://www.netdata.cloud"> <meta http-equiv="Refresh" content="0; url=https://www.netdata.cloud">
<meta charset=utf-8> <meta charset=utf-8>
<title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title> <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
<meta name=author content="Costa Tsaousis"> <meta name=author content="Costa Tsaousis">
<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."> <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.">

2
web/gui/dashboard/demosites2.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData - Real-time performance monitoring, done right!</title> <title>Netdata - Real-time performance monitoring, done right!</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/gui/dashboard/index-node-view.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData TV Dashboard</title> <title>Netdata TV Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/gui/dashboard/infographic.html
View file

@ -3,7 +3,7 @@
<html lang=en-us> <html lang=en-us>
<head> <head>
<meta charset=utf-8> <meta charset=utf-8>
<title>NetData: Get control of your Linux Servers. Simple. Effective. Awesome.</title> <title>Netdata: Get control of your Linux Servers. Simple. Effective. Awesome.</title>
<meta name=author content="Costa Tsaousis"> <meta name=author content="Costa Tsaousis">
<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."> <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.">

2
web/gui/dashboard/tv-react.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData TV Dashboard</title> <title>Netdata TV Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/gui/dashboard/tv.html
View file

@ -2,7 +2,7 @@
<!-- SPDX-License-Identifier: GPL-3.0-or-later --> <!-- SPDX-License-Identifier: GPL-3.0-or-later -->
<html lang="en"> <html lang="en">
<head> <head>
<title>NetData TV Dashboard</title> <title>Netdata TV Dashboard</title>
<meta name="application-name" content="netdata"> <meta name="application-name" content="netdata">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

2
web/server/web_client.c
View file

@ -1177,7 +1177,7 @@ void web_client_build_http_header(struct web_client *w) {
buffer_sprintf(w->response.header_output, buffer_sprintf(w->response.header_output,
"HTTP/1.1 %d %s\r\n" "HTTP/1.1 %d %s\r\n"
"Connection: %s\r\n" "Connection: %s\r\n"
"Server: NetData Embedded HTTP Server %s\r\n" "Server: Netdata Embedded HTTP Server %s\r\n"
"Access-Control-Allow-Origin: %s\r\n" "Access-Control-Allow-Origin: %s\r\n"
"Access-Control-Allow-Credentials: true\r\n" "Access-Control-Allow-Credentials: true\r\n"
"Content-Type: %s\r\n" "Content-Type: %s\r\n"