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.
wa...@gmail.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.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Totally unrelated errors from services in our Kubernetes cluster are grouped together in StackDriver. I suppose this is due to the fact that we have similar object hierarchies in our services (PgStore (Db access) - Manager (Business logic) - Controller (API). In this particular case the stack traces are significantly different, as well as the error messages. I am attaching screenshots demonstrating the issue.
What you expected to happen:
Receive two separate StackDriver error groups.
Steps to reproduce: Rebuild the object hierarchy PgStore.ts encapsulated by a Manager.ts and exposed by Controller.ts as an API. Throw the same errors.
Other information (workarounds you have tried, documentation consulted, etc): N/A