Assigned
Status Update
No update yet.
Comments
ca...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
ba...@google.com
ba...@google.com
ra...@sabre.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.
al...@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 using Google Trace and examining the traces using Cloud Logging Logs Explorer, the message "No Logs found for this trace" is encountered, even when inspecting the trace with the corresponding
trace id.The LogEntry
traceIduses the formatprojects/PROJECT/traces/TRACE_ID(notTRACE_ID) and thisPROJECTvalue does not match the value of the project whose trace is currently being inspected. Meaning that the issue only appears when logs are copied across projects.What you expected to happen:
The expected behavior is to be able to inspect them in the trace details, regardless of which project they are created on.
Other information (workarounds you have tried, documentation consulted, etc):
The only workaround currently is to inspect the trace from the project they were created.