Assigned
Status Update
No update yet.
Comments
ma...@google.com
ma...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
[Deleted User] <[Deleted User]>
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.
ba...@google.com
ba...@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.
Description
FEATURE REQUEST
Business Impact: Currently, “time” keyword in GKE Logs take precedence over the timestamp from container runtime, which results in distorted sorting of logs by timestamp and complicates log analysis, investigations and troubleshooting.
What you would like to accomplish: I would like that the timestamp from container runtime doesn't get overwritten by the “time” keyword.
How this might work: Remove the dependency on this behavior, remove the special behavior of
timekeyword so that it no longer takes precedence over container runtime timestamp.If applicable, reasons why alternative solutions are not sufficient: No workarounds
Other information (workarounds you have tried, documentation consulted, etc): The behavior is