e7b6fe7f6 · cryptotaxi247/netdata-1

aclk/aclk.c

+3 -3

@@ -121,7 +121,7 @@ static int wait_till_agent_claimed(void)

121 * agent claimed, cloud url set and private key available

122 *

123 * @param aclk_hostname points to location where string pointer to hostname will be set

124 - * @param ackl_port port to int where port will be saved

124 + * @param aclk_port port to int where port will be saved

125 *

126 * @return If non 0 returned irrecoverable error happened and ACLK should be terminated

127 */

@@ -212,7 +212,7 @@ static void msg_callback_old_protocol(const char *topic, const void *msg, size_t

212 close(logfd);

213 #endif

214

215 - debug(D_ACLK, "Got Message From Broker Topic \"%s\" QOS %d MSG: \"%s\"", topic, qos, cmsg);

215 + debug(D_ACLK, "Got Message From Broker Topic \"%s\" QoS %d MSG: \"%s\"", topic, qos, cmsg);

216

217 if (strcmp(cmd_topic, topic))

218 error("Received message on unexpected topic %s", topic);

@@ -303,7 +303,7 @@ static int read_query_thread_count()

303

304 void aclk_graceful_disconnect(mqtt_wss_client client);

305

306 -/* Keeps connection alive and handles all network comms.

306 +/* Keeps connection alive and handles all network communications.

307 * Returns on error or when netdata is shutting down.

308 * @param client instance of mqtt_wss_client

309 * @returns 0 - Netdata Exits

aclk/aclk_rx_msgs.c

+1 -1

@@ -227,7 +227,7 @@ int aclk_handle_cloud_message(char *payload)

227 // see what `aclk_queue_query` parameter `internal` does

228

229 // NEVER CONTINUE THIS LOOP AFTER CALLING FUNCTION!!!

230 - // msg handlers (namely aclk_handle_version_responce)

230 + // msg handlers (namely aclk_handle_version_response)

231 // can freely change what aclk_incoming_msg_types points to

232 // so either exit or restart this for loop

233 freez(cloud_to_agent.type_id);

aclk/aclk_tx_msgs.c

+1 -1

@@ -188,7 +188,7 @@ static struct json_object *create_hdr(const char *type, const char *msg_id, time

188

189 // TODO handle this somehow on older json-c

190 // tmp = json_object_new_uint64(ts_us);

191 -// probably jso->_to_json_strinf -> custom function

191 +// probably jso->_to_json_string -> custom function

192 // jso->o.c_uint64 -> map this with pointer to signed int

193 // commit that implements json_object_new_uint64 is 3c3b592

194 // between 0.14 and 0.15

collectors/COLLECTORS.md

+1 -1

@@ -338,7 +338,7 @@ configure any of these collectors according to your setup and infrastructure.

338 statistics using information provided by `ngx_http_reqstat_module`.

339 - [Tomcat](/collectors/python.d.plugin/tomcat/README.md): Collect web server performance metrics from the Manager App

340 (`/manager/status?XML=true`).

341 -- [Traefik](/collectors/python.d.plugin/traefik/README.md): Uses Trafik's Health API to provide statistics.

341 +- [Traefik](/collectors/python.d.plugin/traefik/README.md): Uses Traefik's Health API to provide statistics.

342 - [Varnish](/collectors/python.d.plugin/varnish/README.md): Provides HTTP accelerator global, backends (VBE), and

343 disks (SMF) statistics using the `varnishstat` tool.

344 - [x509 check](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/x509check/): Monitor certificate

collectors/ebpf.plugin/README.md

+1 -1

@@ -605,7 +605,7 @@ The eBPF collector enables and runs the following eBPF programs by default:

605 - `fd` : This eBPF program creates charts that show information about calls to open files.

606 - `mount`: This eBPF program creates charts that show calls to syscalls mount(2) and umount(2).

607 - `shm`: This eBPF program creates charts that show calls to syscalls shmget(2), shmat(2), shmdt(2) and shmctl(2).

608 -- `sync`: Montitor calls to syscalls sync(2), fsync(2), fdatasync(2), syncfs(2), msync(2), and sync_file_range(2).

608 +- `sync`: Monitor calls to syscalls sync(2), fsync(2), fdatasync(2), syncfs(2), msync(2), and sync_file_range(2).

609 - `network viewer`: This eBPF program creates charts with information about `TCP` and `UDP` functions, including the

610 bandwidth consumed by each.

611 - `vfs`: This eBPF program creates charts that show information about VFS (Virtual File System) functions.

collectors/ebpf.plugin/ebpf.d.conf

+1 -1

@@ -41,7 +41,7 @@

41 # `socket` : This eBPF program creates charts with information about `TCP` and `UDP` functions, including the

42 # bandwidth consumed by each.

43 # `softirq` : Monitor latency of serving software interrupt requests (soft IRQs).

44 -# `sync` : Montitor calls for syscall sync(2).

44 +# `sync` : Monitor calls for syscall sync(2).

45 # `swap` : Monitor calls for internal swap functions.

46 # `vfs` : This eBPF program creates charts that show information about process VFS IO, VFS file manipulation and

47 # files removed.

collectors/ebpf.plugin/ebpf_cachestat.h

+1 -1

@@ -52,7 +52,7 @@ enum cachestat_indexes {

52 NETDATA_CACHESTAT_IDX_MISS

53 };

54

55 -enum cachesta_tables {

55 +enum cachestat_tables {

56 NETDATA_CACHESTAT_GLOBAL_STATS,

57 NETDATA_CACHESTAT_PID_STATS

58 };

collectors/ebpf.plugin/ebpf_sync.h

+1 -1

@@ -47,7 +47,7 @@ enum netdata_sync_charts {

47 };

48

49 enum netdata_sync_table {

50 - NETDATA_SYNC_GLOBLAL_TABLE

50 + NETDATA_SYNC_GLOBAL_TABLE

51 };

52

53 extern void *ebpf_sync_thread(void *ptr);

collectors/node.d.plugin/sma_webbox/README.md

+1 -1

@@ -6,7 +6,7 @@ sidebar_label: "SMA Sunny WebBox"

6

7 # SMA Sunny WebBox monitoring with Netdata

8

9 -Montiroing for the [SMA Sunny

9 +Monitoring for the [SMA Sunny

10 WebBox](https://www.sma-sunny.com/en/questions-and-answers-on-discontinuation-of-the-sunny-webbox/).

11

12 The module supports any number of name servers:

collectors/python.d.plugin/web_log/README.md

+1 -1

@@ -120,7 +120,7 @@ This is a nice view of the traffic the web server is receiving and is sending.

120

121 What is important to know for this chart, is that the bandwidth used for each request and response is accounted at the time the log is written. Since [**netdata**](https://my-netdata.io/) refreshes this chart every single second, you may have unrealistic spikes is the size of the requests or responses is too big. The reason is simple: a response may have needed 1 minute to be completed, but all the bandwidth used during that minute for the specific response will be accounted at the second the log line is written.

122

123 -As the legend on the chart suggests, you can use FireQoS to setup QoS on the web server ports and IPs to accurately measure the bandwidth the web server is using. Actually, [there may be a few more reasons to install QoS on your servers](/collectors/tc.plugin/README.md#tcplugin)...

123 +As the legend on the chart suggests, you can use FireQOS to setup QoS on the web server ports and IPs to accurately measure the bandwidth the web server is using. Actually, [there may be a few more reasons to install QoS on your servers](/collectors/tc.plugin/README.md#tcplugin)...

124

125 **Bandwidth** KB/s

126

collectors/statsd.plugin/README.md

+1 -1

@@ -532,7 +532,7 @@ Using the client library by [sivy/node-statsd](https://github.com/sivy/node-stat

532 You can also use StatsD with:

533 - Golang, thanks to [alexcesaro/statsd](https://github.com/alexcesaro/statsd)

534 - Ruby, thanks to [reinh/statsd](https://github.com/reinh/statsd)

535 -- Java, thanks to [DataDog/java-docstatsd-client](https://github.com/DataDog/java-dogstatsd-client)

535 +- Java, thanks to [DataDog/java-dogstatsd-client](https://github.com/DataDog/java-dogstatsd-client)

536

537

538 ### Shell

collectors/tc.plugin/tc-qos-helper.sh.in

+3 -3

@@ -89,13 +89,13 @@ if [ ! -d "${fireqos_run_dir}" ]; then

89 if [ -d "${LOCALSTATEDIR}/run/fireqos" ]; then

90 fireqos_run_dir="${LOCALSTATEDIR}/run/fireqos"

91 else

92 - warning "FireQoS is installed as '${fireqos}', its installation config at '${fireqos_exec_dir}/install.config' specifies local state data at '${LOCALSTATEDIR}/run/fireqos', but this directory is not found or is not readable (check the permissions of its parents)."

92 + warning "FireQOS is installed as '${fireqos}', its installation config at '${fireqos_exec_dir}/install.config' specifies local state data at '${LOCALSTATEDIR}/run/fireqos', but this directory is not found or is not readable (check the permissions of its parents)."

93 fi

94 else

95 - warning "Although FireQoS is installed on this system as '${fireqos}', I cannot find/read its installation configuration at '${fireqos_exec_dir}/install.config'."

95 + warning "Although FireQOS is installed on this system as '${fireqos}', I cannot find/read its installation configuration at '${fireqos_exec_dir}/install.config'."

96 fi

97 else

98 - warning "FireQoS is not installed on this system. Use FireQoS to apply traffic QoS and expose the class names to netdata. Check https://github.com/netdata/netdata/tree/master/collectors/tc.plugin#tcplugin"

98 + warning "FireQOS is not installed on this system. Use FireQOS to apply traffic QoS and expose the class names to netdata. Check https://github.com/netdata/netdata/tree/master/collectors/tc.plugin#tcplugin"

99 fi

100 fi

101

database/sqlite/sqlite3.c

+1 -1

@@ -124427,7 +124427,7 @@ insert_cleanup:

124427 /* This is the Walker callback from sqlite3ExprReferencesUpdatedColumn().

124428 * Set bit 0x01 of pWalker->eCode if pWalker->eCode to 0 and if this

124429 ** expression node references any of the

124430 -** columns that are being modifed by an UPDATE statement.

124430 +** columns that are being modified by an UPDATE statement.

124431 */

124432 static int checkConstraintExprNode(Walker *pWalker, Expr *pExpr){

124433 if( pExpr->op==TK_COLUMN ){

docs/anonymous-statistics.md

+1 -1

@@ -30,7 +30,7 @@ You can opt-out from sending anonymous statistics to Netdata through three diffe

30

31 ## Agent Dashboard - PostHog JavaScript

32

33 -When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata will initialiszes a PostHog session and masks various event attributes.

33 +When you kick off an Agent dashboard session by visiting `http://NODE:19999`, Netdata initializes a PostHog session and masks various event attributes.

34

35 _Note_: You can see the relevant code in the [dashboard repository](https://github.com/netdata/dashboard/blob/master/src/domains/global/sagas.ts#L107) where the `window.posthog.register()` call is made.

36

docs/guides/monitor/kubernetes-k8s-netdata.md

+1 -1

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

1 <!--

2 title: "Kubernetes monitoring with Netdata: Overview and visualizations"

3 -description: "Learn how to navigate Netdata's Kubernetes monitoring features for visualizing the health and performance of a Kubernetes cluster with per-second granulrity."

3 +description: "Learn how to navigate Netdata's Kubernetes monitoring features for visualizing the health and performance of a Kubernetes cluster with per-second granularity."

4 image: /img/seo/guides/monitor/kubernetes-k8s-netdata.png

5 author: "Joel Hans"

6 author_title: "Editorial Director, Technical & Educational Resources"

docs/guides/monitor/lamp-stack.md

+1 -1

@@ -89,7 +89,7 @@ metrics](https://httpd.apache.org/docs/2.4/mod/mod_status.html), which is just _

89

90 The Netdata Agent also comes with a [web log

91 collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/weblog), which reads Apache's access

92 -log file, procesess each line, and converts them into per-second metrics. On Debian systems, it reads the file at

92 +log file, processes each line, and converts them into per-second metrics. On Debian systems, it reads the file at

93 `/var/log/apache2/access.log`.

94

95 At installation, the Netdata Agent adds itself to the [`adm`

docs/guides/monitor/statsd.md

+2 -2

@@ -266,9 +266,9 @@ The `info` field supports `html`, embedding useful links and instructions in the

266

267 ## Vendoring a new collector

268

269 -After all this hussle, not only did we illustrate how to visualize any data source in Netdata using the StatsD protocol, but we have also created a new collector in the process.

269 +While we learned how to visualize any data source in Netdata using the StatsD protocol, we have also created a new collector.

270

271 -While using the same underlying collector-StatsD-every new `myapp.conf` file will in essence create a new data source and dashboard section for Netdata. While Netdata will load all the configuration files by default, it will **not** create dashboard sections or charts, unless it start receiving data for that particular data source. This means that we can now share our collector with the rest of the Netdata community.

271 +As long as you use the same underlying collector, every new `myapp.conf` file will create a new data source and dashboard section for Netdata. Netdata loads all the configuration files by default, but it will **not** create dashboard sections or charts, unless it starts receiving data for that particular data source. This means that we can now share our collector with the rest of the Netdata community.

272

273 If you want to contribute or you need any help in developing your collector, we have a whole [Forum Category](https://community.netdata.cloud/c/agent-development/9) dedicated to contributing to the Netdata Agent.

274

docs/guides/python-collector.md

+1 -1

@@ -433,7 +433,7 @@ weather_station_1:

433 name: 'Greece'

434 endpoint: 'https://endpoint_1.com'

435 port: 67

436 - type: 'celcius'

436 + type: 'celsius'

437 weather_station_2:

438 name: 'Florida USA'

439 endpoint: 'https://endpoint_2.com'

packaging/installer/install-required-packages.sh

+2 -2

@@ -124,9 +124,9 @@ Supported packages (you can append many of them):

124

125 - sensors install lm_sensors for monitoring h/w sensors

126

127 - - firehol-all packages required for FireHOL, FireQoS, update-ipsets

127 + - firehol-all packages required for FireHOL, FireQOS, update-ipsets

128 - firehol packages required for FireHOL

129 - - fireqos packages required for FireQoS

129 + - fireqos packages required for FireQOS

130 - update-ipsets packages required for update-ipsets

131

132 - demo packages required for running a netdata demo site

web/gui/dashboard/dashboard.js

+1 -1

@@ -6957,7 +6957,7 @@ let chartState = function (element) {

6957 resizeChartToHeight(this.height_original.toString());

6958 }

6959

6960 - // else if the current height is not the firstchild's clientheight

6960 + // else if the current height is not the firstChild's clientheight

6961 // resize to it

6962 else if (typeof this.element_legend_childs.perfect_scroller.firstChild !== 'undefined') {

6963 let parent_rect = this.element.getBoundingClientRect();

web/gui/dashboard_info.js

+1 -1

@@ -683,7 +683,7 @@ netdataDashboard.menu = {

683 'or <code>inactive</code> (meaning stopped, unbound, unplugged), ' +

684 'as well as in the process of being activated or deactivated, i.e. between the two states (these states are called <code>activating</code>, <code>deactivating</code>). ' +

685 'A special <code>failed</code> state is available as well, which is very similar to <code>inactive</code> and is entered when the service failed in some way (process returned error code on exit, or crashed, an operation timed out, or after too many restarts). ' +

686 - 'For detailes, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.html" target="_blank"> systemd(1)</a>.'

686 + 'For details, see <a href="https://www.freedesktop.org/software/systemd/man/systemd.html" target="_blank"> systemd(1)</a>.'

687 },

688

689 'changefinder': {

web/gui/src/dashboard.js/main.js

+1 -1

@@ -1771,7 +1771,7 @@ let chartState = function (element) {

1771 resizeChartToHeight(this.height_original.toString());

1772 }

1773

1774 - // else if the current height is not the firstchild's clientheight

1774 + // else if the current height is not the firstChild's clientheight

1775 // resize to it

1776 else if (typeof this.element_legend_childs.perfect_scroller.firstChild !== 'undefined') {

1777 let parent_rect = this.element.getBoundingClientRect();

Spelling (#10976)