Assigned
Status Update
No update yet.
Comments
sa...@google.com
sa...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
sa...@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.
[Deleted User] <[Deleted User]>
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
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:
I am trying to test GCP Error reporting by creating a cloud function that throws exceptions/errors when I run it,
In the logs, I can see the errors and I can use Log-based alerts
But on the Error reporting page, I only see a message saying Setup Error reporting, which will take me to a document rather than an action, in the document it's explicitly mentioned that error reporting API will be enabled automatically for cloud function without the need to use packages
What you expected to happen:
I expected to get error reports in the error reporting api
Steps to reproduce:
Enable Error Reporting API
Enable Cloud Function Needed APIs
Create a cloud function using:
Language: Python 3.11
Trigger: HTTPS requests
Code: A simple python code that will generate Error messages in the logs in case the input arguments contain "F" in the message attribute.
Trigger the Function and make it fail
In the logs there will be Error logs with traceback, in the reporting API there will be nothing
Other information (workarounds you have tried, documentation consulted, etc):