You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
It would be great if AppRunner could either publish some kind of event whenever it disconnects a client due to its request timeout of 120 seconds (as of 2024 - see also #104), or if it could at least publish metrics on how often it did so. Ideally, these metrics should be shown in the Metrics panel of the AppRunner console.
Describe alternatives you've considered
As far as I can tell, the only way we are able to figure out if something got disconnected due to AppRunner itself vs e.g. a client disconnecting from their end is to look at the time the request took before it was disconnected - if it's around 120 seconds, it was probably done by AppRunner. This isn't very convenient or exact, though.
Additional context
Attachments
The text was updated successfully, but these errors were encountered:
Community Note
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
It would be great if AppRunner could either publish some kind of event whenever it disconnects a client due to its request timeout of 120 seconds (as of 2024 - see also #104), or if it could at least publish metrics on how often it did so. Ideally, these metrics should be shown in the Metrics panel of the AppRunner console.
Describe alternatives you've considered
As far as I can tell, the only way we are able to figure out if something got disconnected due to AppRunner itself vs e.g. a client disconnecting from their end is to look at the time the request took before it was disconnected - if it's around 120 seconds, it was probably done by AppRunner. This isn't very convenient or exact, though.
Additional context
Attachments
The text was updated successfully, but these errors were encountered: