summaryrefslogtreecommitdiffstats
path: root/backends
diff options
context:
space:
mode:
authorJoeWrightss <42261994+JoeWrightss@users.noreply.github.com>2019-04-01 04:19:55 +0800
committerChris Akritidis <43294513+cakrit@users.noreply.github.com>2019-03-31 22:19:55 +0200
commitb92e9d84eb96992ee6f3b4a83fc11a0b1b063a81 (patch)
treeb7cb8a776f205dae47ba39fe062b25094056e69b /backends
parente382de8e7cd47f50a2bc3862bdc2b20b2c47f3d2 (diff)
Fix some misspells in docs and code (#5549)
Signed-off-by: zhoulin xie <zhoulin.xie@daocloud.io>
Diffstat (limited to 'backends')
-rw-r--r--backends/WALKTHROUGH.md6
-rw-r--r--backends/prometheus/README.md4
-rw-r--r--backends/prometheus/backend_prometheus.c8
3 files changed, 9 insertions, 9 deletions
diff --git a/backends/WALKTHROUGH.md b/backends/WALKTHROUGH.md
index 0c330ee1a3..d3666ef5db 100644
--- a/backends/WALKTHROUGH.md
+++ b/backends/WALKTHROUGH.md
@@ -209,7 +209,7 @@ 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
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 homogeneus chart "system.cpu", context "system.cpu", family
+comments `# COMMENT homogeneous chart "system.cpu", context "system.cpu", family
"cpu", units "percentage"` Followed by the metrics. This is a good start now let
us drill down to the specific metric we would like to graph.
@@ -251,9 +251,9 @@ http://localhost:19999/api/v1/allmetrics?format=prometheus&help=yes&types=yes&so
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 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
+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 metrics returned by
-NetData’s internal database (not specifying any source= url parameter) then use
+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 chart.
diff --git a/backends/prometheus/README.md b/backends/prometheus/README.md
index 4a6cbfee2d..6b070dea8d 100644
--- a/backends/prometheus/README.md
+++ b/backends/prometheus/README.md
@@ -250,7 +250,7 @@ If you search that page for `"system.cpu"` you will find all the metrics netdata
Searching for `"system.cpu"` reveals:
```sh
-# COMMENT homogeneus chart "system.cpu", context "system.cpu", family "cpu", units "percentage"
+# COMMENT homogeneous chart "system.cpu", context "system.cpu", family "cpu", units "percentage"
# COMMENT netdata_system_cpu_percentage_average: dimension "guest_nice", value is percentage, gauge, dt 1500066653 to 1500066662 inclusive
netdata_system_cpu_percentage_average{chart="system.cpu",family="cpu",dimension="guest_nice"} 0.0000000 1500066662000
# COMMENT netdata_system_cpu_percentage_average: dimension "guest", value is percentage, gauge, dt 1500066653 to 1500066662 inclusive
@@ -279,7 +279,7 @@ In `average` or `sum` data sources, all values are normalized and are reported t
If the data source was `as collected`, the response would be:
```sh
-# COMMENT homogeneus chart "system.cpu", context "system.cpu", family "cpu", units "percentage"
+# COMMENT homogeneous chart "system.cpu", context "system.cpu", family "cpu", units "percentage"
# COMMENT netdata_system_cpu_total: chart "system.cpu", context "system.cpu", family "cpu", dimension "guest_nice", value * 1 / 1 delta gives percentage (counter)
netdata_system_cpu_total{chart="system.cpu",family="cpu",dimension="guest_nice"} 0 1500066716438
# COMMENT netdata_system_cpu_total: chart "system.cpu", context "system.cpu", family "cpu", dimension "guest", value * 1 / 1 delta gives percentage (counter)
diff --git a/backends/prometheus/backend_prometheus.c b/backends/prometheus/backend_prometheus.c
index f05da06972..3641b07c5a 100644
--- a/backends/prometheus/backend_prometheus.c
+++ b/backends/prometheus/backend_prometheus.c
@@ -305,13 +305,13 @@ static void rrd_stats_api_v1_charts_allmetrics_prometheus(RRDHOST *host, BUFFER
rrdset_rdlock(st);
int as_collected = (BACKEND_OPTIONS_DATA_SOURCE(backend_options) == BACKEND_SOURCE_DATA_AS_COLLECTED);
- int homogeneus = 1;
+ int homogeneous = 1;
if(as_collected) {
if(rrdset_flag_check(st, RRDSET_FLAG_HOMEGENEOUS_CHECK))
rrdset_update_heterogeneous_flag(st);
if(rrdset_flag_check(st, RRDSET_FLAG_HETEROGENEOUS))
- homogeneus = 0;
+ homogeneous = 0;
}
else {
if(BACKEND_OPTIONS_DATA_SOURCE(backend_options) == BACKEND_SOURCE_DATA_AVERAGE && !(output_options & PROMETHEUS_OUTPUT_HIDEUNITS))
@@ -320,7 +320,7 @@ static void rrd_stats_api_v1_charts_allmetrics_prometheus(RRDHOST *host, BUFFER
if(unlikely(output_options & PROMETHEUS_OUTPUT_HELP))
buffer_sprintf(wb, "\n# COMMENT %s chart \"%s\", context \"%s\", family \"%s\", units \"%s\"\n"
- , (homogeneus)?"homogeneus":"heterogeneous"
+ , (homogeneous)?"homogeneous":"heterogeneous"
, (output_options & PROMETHEUS_OUTPUT_NAMES && st->name) ? st->name : st->id
, st->context
, st->family
@@ -348,7 +348,7 @@ static void rrd_stats_api_v1_charts_allmetrics_prometheus(RRDHOST *host, BUFFER
suffix = "_total";
}
- if(homogeneus) {
+ if(homogeneous) {
// all the dimensions of the chart, has the same algorithm, multiplier and divisor
// we add all dimensions as labels