Description of problem: In RHCI we require the ability of the 'foreman' user to be able to read the logs generated by 'foreman-proxy'. Currently the logs for /var/log/foreman-proxy are owned by: foreman-proxy:foreman-proxy and they are 750. We need 'foreman' to be able to read these logs. In general, RHCI requests that the 'foreman' user has access to read all logs generated by Satellite-6.
Dmitri - does your work on exposing proxy status via the API can be an alternative to parsing log files?
Smart-proxy's log module provides access to smart-proxy logs. Those can be accessed via /log api end point.
Moving 6.2 bugs out to sat-backlog.
Since satellite 6.2 the smart proxy component has an API to return its logs, it can be visible under the infra -> capsules -> select the one you wish, assuming it has the proxy log feature enabled. You may also parse this information via a plugin, or a rest api call to the proxy if you are developing a plugin on top of satellite. I'm closing this due to the above, please re-open if you disagree. thanks!