Assigned
Status Update
No update yet.
Comments
be...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
ha...@arrivy.com
Hello! Sorry to bring up this issue after almost a year but I wanted to add that we have chosen metric identifier as agent.googleapis.com/memory/percent_used but autoscaling didnt work out for us either. It would be appraciated if you can guide us.
be...@google.com
Hi, at the moment we are using the cpu_utilization/target_utilization attribute (in app.yaml) for autoscaling in the app engine flexible environment, however it would be great if we can have the way to mention the memory_utilization metrics as well to decide on the auto scaling. It will give us more control of the auto scaling the instances than now.
ha...@arrivy.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
Description
Right now the application deployed on the app engine can accept requests being made from any TLS version i.e. 1.0. 1.2, 1.3. But, the Stackdriver does not give any information about the TLS version. Due to which one can not get to know about the TLS version and hence can not analyze the security level of the app.
What you would like to accomplish:
Add the TLS version with the trace of each API request.
How this might work:
Show the request TLS version in the "protoPayload" section of the Stackdriver trace.
If applicable, reasons why alternative solutions are not sufficient:
Other information (workarounds you have tried, documentation consulted, etc):