Product ManagerProduct Managerthis is the ultimate goal for Logicmonitor
Hi Axshey, what is the ultimate goal? Why are you trying to move away from root? This makes running collectors in containers harder since they typically don’t have any user besides root.
Is there a propertysource you’ve written that will tell me which collectors are running as root vs. non-root? When we do the install, we run it with sudo and it creates the logicmonitor user. Neither of which are using the root account (depending on your philosophy on sudo).
Come to think of it, I need a propertysource that shows the user for each of my collectors (windows too), so i may just write it. Might make it a configsource so i can keep the history.
If you go to your collectors page → Click on on “Manage” for the collector in question → Go to Collector status, you can find the root/non-root status of the collector
If you are installing the Linux collector using the logicmonitor user created, you dont have to take any action. It is running as a non-root user then.
We are pursuing non-root privileges for the collector because:
1) It will limit damages in case a vulnerability is exploited by an attacker.
2) It helps you pass security audits if a security conscious customer demands it.
3) The collector does not need to run at max privilege in order to monitor most devices and running software applications in the least privilege mode is security best practice