martastain
commented
1 week ago I don't think this is a good solution.
Forwarding log messages to the server would cause a significant overhead. Ash already collects and unifies logging from spawned services, so monitoring just the worker service should be enough. For viewing logs (if docker compose logs -f worker is not enough / viable option) i'd suggest a docker log driver for log management of choice - such as loki: https://grafana.com/docs/loki/latest/send-data/docker-driver/
Also keep in mind forwarding logs to server wouldn't help you if the problem is the server connection itself
Please describe the feature you have in mind and explain what the current shortcomings are?
A couple of clients would like to see the logs from services to better debugging. (e.g. Tony creates his own Shotgrid services). In Event viewer they can see only logs from Ayon server. If it is not possible to redirect logs from services to Event viewer there could be a special debugging tool. So far all cloud logs are accessible in ArgoCD which is behind AWS VPN. This issue has been already discussed with Lablabs, they might come up with some plan how to distibute logs in a better way.
How would you imagine the implementation of the feature?
No response
Describe alternatives you've considered:
No response
Additional context:
link to discussion on Discord (might be a private channel)
This issue was automatically created from Clickup ticket AY-7117