How to configure centralized logging?
1. Update the policy
Add the below policy variables to the beginning of the policy, for example in "/etc/opt/quest/qpm4u/pm.conf" add.
iologhost="centrallogmaster.domain.local"; eventloghost="centrallogmaster.domain.local"; tmplogdir="/opt/quest/qpm4u/iologs/queue";
Note: Where "iologhost" and "eventloghost" contain the hostname of the master where the logs will reside.
2. Update the settings file
On the central log master, add/update the "clients" setting in "/etc/opt/quest/qpm4u/pm.setting" to include each of the masters which will be permitted to forward its logs to the central log master. For example;
clients master1.democorp.local master2.democorp.local master3.democorp.local
In 5.5, centralized logging has been improved to simplify the configuration and distribute the collection of keystroke data across the cluster. The authorizing Master will now collect the keystroke data from the Agent and forward the data onto the Central Log Master at the end of the session rather than the Log Master collecting the keystroke data directly. In addition to reducing the load on the Log Master the configuration has been simplified by changing the “clients” setting on the Log Master to require a list of Masters rather than all your Agents.
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center