Non-Root Access for SysEdge HostMonitoring

Products

• DX SaaS

Issue/Introduction

Background:  Using the APM Infra Agent on Linux host with non-root access and using prescribed direction from the documentation.

Installing Infrastructure Agent on DX Experience Insights

Reviewing the value statement of one of these two (2) methods:

1. Start as a non-root user without the sudo permission.
./APMIACtrl.sh console_start

2. Install as a Root User and Assign the APMIA service to a Non-Root User

./APMIACtrl.sh install user=<username>

Challenge:  Attempting to leverage the extension of HostMonitoring with sysedge process.

This process appears to have a challenge with non-root access but appears to be documented process in  Sysedge User's Guide

"Configure User and Group Permissions for Subprograms (UNIX Only)
By default, the SystemEDGE agent runs subprograms (for example, remote shell, action,
and extension object invocations) with its effective user and group permissions,
normally root. Depending on the local security policies in effect, you may want to set
the agent to use actions and extension objects that run with different user and group
permissions.
To run subprograms with the effective user and group permissions of a user other than
root, add the following lines to the sysedge.cf file:
subprogram_user_name <name>
subprogram_group_name <name>"


We want to explore this feature, but we are seeing a deployment challenge via this method:

2. Install as a Root User and Assign the APMIA service to a Non-Root User

./APMIACtrl.sh install user=<username>

The sysedge process when it starts is copying data to /etc for  sysedge.cf   (this appears unnecessary, as the sysedge.cf file is maintained under the installed folder).    Noticed a conflict between the systemd apmia.service and sysedge.service.   The sysedge.service will fail, due to the apmia.service has already started a copy of the sysedge process

Request: Clarify steps for non-root  with HostMonitoring (aka sysedge process)
2. Install as a Root User and Assign the APMIA service to a Non-Root User

./APMIACtrl.sh install user=<username>

Is there an environmental variable that may be set to avoid coping a file to /etc/  and prevent the duplicate systemd service for sysedge (that is managed by apmia service)?

Versions:
apmia-unix v2023.9.1.16:2023.9.1.16
systemedge-unix v2023.9.1.16:2023.9.1.16
hostmonitor v2023.9.1.16:2023.9.1.16

Environment

Release : SAAS

Resolution

This is an enhancement request to be reviewed by product management.