I have been experiencing issues with my machine logs on the ams region in 3 different ways:
When using flyctl logs, I can retrieve the logs for my application on the ams region. However, the logs do not auto-update in my terminal. I have to close and re-run the command to get latest logs.
When looking at the monitoring tab on the webpage, I also get logs for the app, but with the same issue: they do not auto-update. I need to refresh the page to get the latest logs.
I have a staging application in the lhs region, which is successfully auto-updating the logs in the terminal, in the UI, and is succeeding in shipping my logs to Loki and Logtail.
The region my production app is deployed to is switching every deploy (between lhs and ams), so this is quite frustrating. Is there an issue with the ams region, or is this intended?
Actually, it kinda works on a new app I just created (wooninzicht is the app name). The logs from the web process do not show until I restart fly logs. The logs from schedulerdo show in real-time.