Although most Linux distributions ship with some basic monitoring tools, they rarely offer in-depth solutions that can tell you exactly which processes are using which amounts of resources. Metricly’s Process Resource Collector comes in handy for acquiring this information. It lets you monitor resource statistics on individual processes.
This article demonstrates how to get started with the Process Resource Collector.
Installation and configuration of Metricly Process Resource Collector
For the purpose of this article, I will assume that you have a base-build CentOS 7 x64 server which is fully up-to-date. You should run all commands as root.
I also assume you are already signed up with Metricly.
With those prerequisites out of the way, the first thing we need to do is log in to the Metricly control panel, go to the “Integrations” tab, and select Linux. Metricly will then display a command for you to run on your Linux box, similar to the one below:
> # sudo N_APIKEY=***REDACTED*** bash -c "$(curl -Ls http://repos.app.netuitive.com/linux.sh)"
Run this command on your server in the CLI. Once it has finished, your server will have the Metricly agent installed and configured, and you should soon see it appear under the “Inventory” tab in your control panel.
When you see the server appear here, you can go ahead and configure the monitoring of individual processes.
Configure monitoring of an individual process
For this part, the first thing to do is to go to the directory where the configuration files are stored. By default, this is located in “/opt/netuitive-agent/conf/collectors”.
> # cd /opt/netuitive-agent/conf/collectors
Next, edit the “ProcessResourcesCollector.conf” file by changing the enabled setting to True. You will also see in this file that there is an example provided that shows how to configure processes to monitor here. “Example_process_name” identifies the process you wish to monitor. In our case this is httpd. “.sample_regex.” is the regex that will be used to capture the process. In our case, this will be “^httpd” in order to catch anything starting with httpd.
Here is an example of what the completed configuration file should look like:
> enabled = True > > [process] > > [[httpd]] > > name = "^httpd" > > [[diamond]] > > selfmon=True
With this in place, you can go ahead and restart the Metricly Linux agent so that the changes take effect, using the following command:
> # systemctl restart netuitive-agent
Once the agent restarts, you can view the stats it is collecting by going to the “Metrics” tab in the Metricly control panel and filtering for process stats. This can be done by clicking the “Metrics” dropdown next to search, and configuring a filter similar to the screenshot below.
It’s as simple as that! You have now configured a simple process to be monitored. Keep in mind that it may take a few minutes to start seeing statistics appear in the dashboard from the newly monitored process.
You can configure a few more advanced options for process monitoring if desired. For details, visit the Metricly documentation.
Adequate monitoring is essential for both performance monitoring and capacity planning. In my operational role, I often find that although a server has been configured for basic monitoring, more advanced features are not possible using the tools installed on the server (such as monitoring open files or collecting detailed information on individual processes).
As you learned from this post, however, Metricly makes it incredibly easy to configure this type of monitoring in order to monitor any application on your server on a per-process basis.
Metricly coaches users throughout their cloud journey to organize, plan, analyze, and optimize their public cloud resources.Try Metricly Free