Monitoring Linux Processes - Best Practice Example  

  RSS

jose
 jose
Active Member
Joined: 9 months ago
Posts: 6
25/06/2019 1:53 am  

In regards to monitoring linux processes on single dashboard (both single instance & multiple instances), would it be possible to mimic in NetDiagnostics the following dashboard as best practice from article  http://devconnected.com/monitoring-linux-processes-using-prometheus-and-grafana/

How can it be achieved in ND? Can you share comparable dashboard screenshot and maybe writeup on building the same?

Key points:

A. system monitoring (cpu + memory) = top/htop like view

B. system availability = in case of a system overload, you may have no physical or remote access to your instance.  By externalizing process monitoring, you can analyze what’s causing the outage without accessing the machine.  Another reason is that processes get created and killed all the time, often by the kernel itself.  With a monitoring dashboard, you can simply go back in time and see which process was causing the issue.


ReplyQuote
Ajit Raul
Member
Joined: 2 years ago
Posts: 3
09/07/2019 11:33 am  

Monitoring Linux System and Processes using NetDiagnostics

In a pre-production and production environment, there are many Linux servers and many processes and services running in each server. These processes are app-based processes doing their tasks.

Many times, there are health issues of the servers due to one or more processes running on server that are using excessive resources which impacts user experience. Most of the time, it is not easy to diagnose the root cause of the issue as issue gets cleared after some time and there is no data available to diagnose the issue.

NetDiagnostics has a comprehensive monitoring, alerting and dashboard capabilities. Using NetDiagnostics, all the metrics of servers and key processes are collected and stored in its big data and retained for several years.

Using this data, NetDiagnostics alerts when any of these metrics are going from ‘normal’ to ‘warning’ state based on the thresholds and give early warning before it reaches critical state. Once alert comes, using correlation, one can find which processes are causing the issue.

Using dashboard, one can see system and process health to see the current state and the trend over last N hours or days or weeks.

Process and System Monitoring

A program loaded into the memory of a Linux computer becomes a process. Processes need to be managed and monitored because they consume system resources like CPU time, memory and disk space. There are also security and safety implications. Monitoring and managing processes is, therefore, an important function of DevOps.

When it comes to process monitoring for Unix systems, you have multiple options using different tools:

The ‘top’ program is a very powerful utility that provides a great deal of information about your running system. This includes data about memory usage, CPU loads, and a list of running processes including the amount of CPU time and memory being utilized by each process. ‘Top’ displays system information in near real-time, updating (by default) every three seconds.

For more details, please click here


ReplyQuote
Share: