You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The procstat input should be able to identify the process to monitor by using the systemd service
Current behavior:
Can only match processes by pidfile, exe, pattern, or user.
Desired behavior:
Match process by specifying systemd service name. systemctl status foo.service provides a Main PID value. This is the value that should be tracked.
Optionally, it might be nice to include any descendent PIDs as well.
Use case: [Why is this important (helps with prioritizing requests)]
Sometimes it might be difficult or impossible to identify a specific process by using the existing matching patterns. Using the systemd service PID could make it easy to identify these.
The text was updated successfully, but these errors were encountered:
Feature Request
Opening a feature request kicks off a discussion.
Proposal:
The
procstat
input should be able to identify the process to monitor by using the systemd serviceCurrent behavior:
Can only match processes by
pidfile
,exe
,pattern
, oruser
.Desired behavior:
Match process by specifying systemd service name.
systemctl status foo.service
provides aMain PID
value. This is the value that should be tracked.Optionally, it might be nice to include any descendent PIDs as well.
Use case: [Why is this important (helps with prioritizing requests)]
Sometimes it might be difficult or impossible to identify a specific process by using the existing matching patterns. Using the systemd service PID could make it easy to identify these.
The text was updated successfully, but these errors were encountered: