Open clemlesne opened 9 months ago
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @calvinsID.
Hi @clemlesne
I notice there is a message cli.__main__: Command ran in 17.648 seconds (init: 0.178, invoke: 17.470)
in the debug log.
The time is too short when using --follow
, is the container in the containerapp restarting at that time?
On the other hand,
az containerapp logs show
:
Show past logs and/or print logs in real time (with the --follow parameter). Note that the logs are only taken from one revision, replica, and container (for non-system logs).
It has Max connection open time, which is by designed.
We recommend you use log analytics to store and search logs.
Monitor logs in Azure Container Apps with Log Analytics | Microsoft Learn
Thanks
Describe the bug
When run, the command
az containerapp logs show --follow
exits after a few seconds. Thus, reading Container Apps logs from a terminal is extremely complicated.Related command
az containerapp logs show --follow
Errors
No error. The process exit abruptly.
Issue script & Debug output
Expected behaviour
Continue to read logs indefinitely.
Environment Summary
Additional context
No response