diff options
Diffstat (limited to 'docs/guides/monitor/process.md')
| -rw-r--r-- | docs/guides/monitor/process.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/guides/monitor/process.md b/docs/guides/monitor/process.md index c1a2d031a8..893e6b7049 100644 --- a/docs/guides/monitor/process.md +++ b/docs/guides/monitor/process.md @@ -15,7 +15,7 @@ and performance of your infrastructure. One of these layers is the _process_. Every time a Linux system runs a program, it creates an independent process that executes the program's instructions in parallel with anything else happening on the system. Linux systems track the state and resource utilization of processes using the [`/proc` filesystem](https://en.wikipedia.org/wiki/Procfs), and -Netdata is designed to hook into those metrics to create meaningul visualizations out of the box. +Netdata is designed to hook into those metrics to create meaningful visualizations out of the box. While there are a lot of existing command-line tools for tracking processes on Linux systems, such as `ps` or `top`, only Netdata provides dozens of real-time charts, at both per-second and event frequency, without you having to write @@ -86,7 +86,7 @@ Linux systems: - Pipes open (`apps.pipes`) - Swap memory - Swap memory used (`apps.swap`) - - Major page faults (i.e. swap activiy, `apps.major_faults`) + - Major page faults (i.e. swap activity, `apps.major_faults`) - Network - Sockets open (`apps.sockets`) - eBPF file @@ -132,7 +132,7 @@ sudo ./edit-config apps_groups.conf Inside the file are lists of process names, oftentimes using wildcards (`*`), that the Netdata Agent looks for and groups together. For example, the Netdata Agent looks for processes starting with `mysqld`, `mariad`, `postgres`, and -others, and groups them into `sql`. That makes sense, since all these procesess are for SQL databases. +others, and groups them into `sql`. That makes sense, since all these processes are for SQL databases. ```conf sql: mysqld* mariad* postgres* postmaster* oracle_* ora_* sqlservr @@ -247,7 +247,7 @@ metrics](https://user-images.githubusercontent.com/1153921/101411810-d08fb800-38 ### Using Netdata's eBPF collector (`ebpf.plugin`) -Netdata's eBPF collector puts its charts in two places. Of most imporance to process monitoring are the **ebpf file**, +Netdata's eBPF collector puts its charts in two places. Of most importance to process monitoring are the **ebpf file**, **ebpf syscall**, **ebpf process**, and **ebpf net** sub-sections under **Applications**, shown in the above screenshot. For example, running the above workload shows the entire "story" how MySQL interacts with the Linux kernel to open @@ -274,7 +274,7 @@ piece of data needed to discover the root cause of an incident. See our [collect setup](/docs/collect/enable-configure.md) doc for details. [Create new dashboards](/docs/visualize/create-dashboards.md) in Netdata Cloud using charts from `apps.plugin`, -`ebpf.plugin`, and application-specific collectors to build targeted dashboards for monitoring key procesess across your +`ebpf.plugin`, and application-specific collectors to build targeted dashboards for monitoring key processes across your infrastructure. Try running [Metric Correlations](https://learn.netdata.cloud/docs/cloud/insights/metric-correlations) on a node that's |