Assigned
Status Update
No update yet.
Comments
ch...@google.com
ch...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
gr...@lytics.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.
ch...@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
Problem you have encountered:
When clicking on a trace or span line in the
Trace detailssection of an individual trace view inTrace explorer, no logs are found when there are in fact matching logs. Using theVIEW LOGSlink pops up a query that results in no results, but incrementing the end time by one millisecond causes the log line to show.What you expected to happen:
I expect all log lines associated with a trace and span to reliably show in the
Trace explorerwindowSteps to reproduce:
View trace detailslink in theLog explorerTrace explorerand see no log lines associatedVIEW LOGSlink and adjust until the query worksOther information (workarounds you have tried, documentation consulted, etc):