After you install an agent on an end point VM, you can monitor existing or custom Linux processes that run on the end point VM.
How to Monitor Linux Services
- From the Manage Telegraf Agents tab, filter by .
- Expand the drop-down arrow against the relevant Linux end point VM on which the agent is installed. You see the Custom Monitoring section.
- Against the Services option, click the vertical ellipsis and then click Add.
- From the Manage Service Activation dialog box, you can add and configure the Linux services to be monitored.
| Option | Description |
|---|---|
| Status | Enable or disable the monitoring of the Linux process. |
| Display Name | Add a suitable name for the Linux process you want to monitor. For new plugin activations, the end point VM name in the format <on VM name>, is automatically appended to the display name. For example, if the display name you enter is <system>, the end point VM name is automatically appended and the name is displayed as <system on VM name>. If the display name was <system on abcd>, after an upgrade, <abcd> is replaced with the end point VM name. If the display name did not end with <on text1>, after an upgrade, <on VM name> is automatically appended to the existing display name. The following are invalid characters and must not be used in the name:<, ", >, and |. |
| Filter Type | Select either Executable Name, Regex Pattern, or Pid File as the filter type from the drop-down menu. |
| Filter Value | The filter value could be a process executable name, a regex pattern, or a pid file absolute path. |
Save the settings to add the Linux service. To edit or delete Linux services, click the Edit or Delete options from the vertical ellipsis against Linux service you added. After the services have been added and saved, click the drop down arrow against Services, to view the list of Linux services and their status.
Metrics Tab
When data is collected successfully, you can view the metric from the Manage Telegraf Agents page, select tab. The metrics for the Linux process are created under an object called Processes which is a single object per end point VM.
