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
amsregion. 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 am using GitHub - superfly/fly-log-shipper: Ship logs from fly to other providers to ship logs to both Loki and Logtail, and in both places I am not getting logs from my application in the
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
ams), so this is quite frustrating. Is there an issue with the
ams region, or is this intended?