Assigned
Status Update
No update yet.
Comments
ma...@google.com
si...@poda.cz Restricted
Restricted
Comment has been deleted.
ma...@google.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.
si...@poda.cz
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.
ba...@google.com
ba...@google.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
Description
Problem you have encountered:
Error Reporting incorrectly groups different python stack traces (with different exception types) into error groups. They are parsed correctly and UI presents them correctly as well, however the grouping is wrong - see attached screenshot. Even exceptions from completely different services are grouped.
What you expected to happen:
Exceptions with stack trace should be grouped by their type as specified inhttps://cloud.google.com/error-reporting/docs/grouping-errors
Steps to reproduce:
Using error reports parsed from GKE logs:
Log two different exception types as an json_payload with stack_trace field value set to exception traceback. Observe errors get grouped together.