Assigned
Status Update
Comments
mp...@siftscience.com <mp...@siftscience.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
re...@google.com <re...@google.com> #3
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.
mp...@siftscience.com <mp...@siftscience.com> #4
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.
mp...@siftscience.com <mp...@siftscience.com> #5
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
ma...@schibsted.com <ma...@schibsted.com> #6
Hello Google team, I was directed to this issue by the support team when we raised concerns around the non availability of memory metrics for Auto Scaling. Is this feature 'released' or in roadmap or not considered ? Please provide some details around this
da...@commercebuild.com <da...@commercebuild.com> #7
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
jo...@packback.co <jo...@packback.co> #8
+1
ad...@mercadolivre.com <ad...@mercadolivre.com> #9
+1
gd...@quickbase.com <gd...@quickbase.com> #10
+ 1
an...@gohitide.com <an...@gohitide.com> #11
+1
pa...@shoper.pl <pa...@shoper.pl> #12
+1
zh...@g.sqex.jp <zh...@g.sqex.jp> #13
+1
ky...@recursion.com <ky...@recursion.com> #14
+1
na...@flumehealth.com <na...@flumehealth.com> #15
+1
ab...@louisvuitton.com <ab...@louisvuitton.com> #16
+1
st...@uber.com <st...@uber.com> #17
+1
an...@uber.com <an...@uber.com> #18
+1
ma...@apollographql.com <ma...@apollographql.com> #19
+1
ro...@strike.me <ro...@strike.me> #20
+1
Has there been any updates with this one?
Has there been any updates with this one?
bo...@estee.com <bo...@estee.com> #21
Its so annoying that I can't use this just because the messages are so uselessly garbled and noisy. Its like the most simple last mile thing that makes the entire service broken.
I also am trying to use the PD integration. The integration itself needs work but even if I could specify my own static summary (a link to docs and dashboard) that would at least be something.
Who on earth finds value in one massive pipe separate string with all of these fields!?
The actual alert with a ton of extraneous info like all the labels
| Violation started...
| Policy: my Policy
| Condition: ...
| View incident: ...
I also am trying to use the PD integration. The integration itself needs work but even if I could specify my own static summary (a link to docs and dashboard) that would at least be something.
Who on earth finds value in one massive pipe separate string with all of these fields!?
The actual alert with a ton of extraneous info like all the labels
| Violation started...
| Policy: my Policy
| Condition: ...
| View incident: ...
al...@vijil.ai <al...@vijil.ai> #22
Comment has been deleted.
ra...@ukg.com <ra...@ukg.com> #23
+1
ni...@gmail.com <ni...@gmail.com> #24
+1
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Give custom Incident Summaries to alert policies so that they are more easily recognizable on the incidents menu and for programmatic functions
How this might work:
Include an "Incident Summary Name" field when creating an Alert Policy
If applicable, reasons why alternative solutions are not sufficient:
When sent off to certain 3rd party tools, like PagerDuty, sometimes the Summary is not enough to immediately be able to take action, delaying response.
Other information (workarounds you have tried, documentation consulted, etc):
The documentation is not sent in this case, so a description of the error in that section would not be recieved.