Assigned
Status Update
Comments
se...@google.com <se...@google.com>
wb...@google.com <wb...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
ro...@google.com <ro...@google.com>
se...@google.com <se...@google.com>
ph...@battelleecology.org <ph...@battelleecology.org> #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.
gr...@trmlabs.com <gr...@trmlabs.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.
to...@gmail.com <to...@gmail.com> #5
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
jd...@amfam.com <jd...@amfam.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...@google.com <da...@google.com> #7
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
hc...@google.com <hc...@google.com> #8
+1 blocker
ph...@battelleecology.org <ph...@battelleecology.org> #9
any update on this, it's critical missing functionality in the API and seems like it must be trivial to fix since the GUI already supports this....
st...@smartcat.io <st...@smartcat.io> #10
+1 Any update? We would like to have this option via terraform.
bf...@benchsci.com <bf...@benchsci.com> #11
+1
yu...@japan-d2.com <yu...@japan-d2.com> #12
+1
ad...@coop.ch <ad...@coop.ch> #13
Comment has been deleted.
ch...@wanteeed.com <ch...@wanteeed.com> #14
+1
ch...@google.com <ch...@google.com>
ch...@google.com <ch...@google.com>
to...@ladbiblegroup.com <to...@ladbiblegroup.com> #15
+1
ma...@ingka.ikea.com <ma...@ingka.ikea.com> #16
+1
er...@sojern.com <er...@sojern.com> #17
+1
[Deleted User] <[Deleted User]> #18
+1
td...@digimarc.com <td...@digimarc.com> #19
+1
ro...@weroad.com <ro...@weroad.com> #20
+1
am...@louisvuitton.com <am...@louisvuitton.com> #21
+1
nm...@apexfintechsolutions.com <nm...@apexfintechsolutions.com> #22
+1
jk...@wisc.edu <jk...@wisc.edu> #23
+1
be...@conv-it.de <be...@conv-it.de> #24
+1
se...@hbt.de <se...@hbt.de> #25
+1 please add this nice quick win. Eidt: Not just quick a win. The API is incomplete, when I have to use the UI anyway.
di...@netrtl.com <di...@netrtl.com> #26
Comment has been deleted.
si...@qbuzz.nl <si...@qbuzz.nl> #27
+1 bur not holding my breath since this is now open for almost 2 years now.
ad...@eee.do <ad...@eee.do> #28
+1
ru...@gmail.com <ru...@gmail.com> #29
+1
vl...@moonactive.com <vl...@moonactive.com> #30
+ 1
hi...@yoodli.ai <hi...@yoodli.ai> #31
+1
si...@oxa.tech <si...@oxa.tech> #32
+1
de...@deloitte.ca <de...@deloitte.ca> #33
Are there any workaround rather than editing on UI?
l....@kt-racing.com <l....@kt-racing.com> #34
+1
an...@gcp.xpand-it.com <an...@gcp.xpand-it.com> #35
+1
st...@missionlane.com <st...@missionlane.com> #36
+1
ju...@gmail.com <ju...@gmail.com> #37
+1
ri...@keepler.io <ri...@keepler.io> #38
+1
ax...@keepler.io <ax...@keepler.io> #39
+1
ju...@keepler.io <ju...@keepler.io> #40
+1
s....@plarium.com <s....@plarium.com> #41
+1
za...@badal.io <za...@badal.io> #42
+1
[Deleted User] <[Deleted User]> #43
+11111
ma...@bcbgroup.io <ma...@bcbgroup.io> #44
+1
ra...@bcbgroup.io <ra...@bcbgroup.io> #45
+1
el...@doppel.com <el...@doppel.com> #46
+1
m....@sap.com <m....@sap.com> #47
+1
va...@point-devel.com <va...@point-devel.com> #48
+1
si...@gmail.com <si...@gmail.com> #49
+1
an...@redso.com.hk <an...@redso.com.hk> #50
+1
c_...@groupon.com <c_...@groupon.com> #51
+1
sk...@google.com <sk...@google.com> #52
+1
ph...@tilt.io <ph...@tilt.io> #53
+1
ba...@nordcloud.com <ba...@nordcloud.com> #54
+1
ni...@unifiedpost.com <ni...@unifiedpost.com> #55
+1
xp...@gmail.com <xp...@gmail.com> #56
+1
eg...@hsbc.com <eg...@hsbc.com> #57
+1
se...@paloaltonetworks.com <se...@paloaltonetworks.com> #58
+1
dt...@r4.ai <dt...@r4.ai> #59
Comment has been deleted.
de...@ag2rlamondiale.fr <de...@ag2rlamondiale.fr> #60
+1
hu...@blocksec.com <hu...@blocksec.com> #61
+1 It's been almost three years now
ng...@randstadusa.com <ng...@randstadusa.com> #62
+1
pa...@hsbc.com <pa...@hsbc.com> #63
+1
ak...@justeattakeaway.com <ak...@justeattakeaway.com> #64
+1 . when can we expect this ?
la...@devoteam.com <la...@devoteam.com> #65
+1
ex...@terveystalo.com <ex...@terveystalo.com> #66
+1
jk...@bgrove.com <jk...@bgrove.com> #67
+1 bueller? bueller? :)
al...@enterprisedb.com <al...@enterprisedb.com> #68
+1
ke...@hangseng.com <ke...@hangseng.com> #69
+1
sk...@google.com <sk...@google.com> #70
For those watching, The REST API documentation shows support for notificationPrompts now.
And someone has merged a fix for terraform google_monitoring_alert_policy,
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Ability to configure notificationPrompts (OPENED, CLOSED) using Monitoring API (and Terraform)
How this might work:
After creation alert policy and exporting its definition to JSON there is flag "notificationPrompts" which cannot be configured via API. There is only "notificationRateLimit" and "autoClose".
Part ojf Alert Policy JSON:
"alertStrategy": {
"autoClose": "604800s",
"notificationPrompts": [
"OPENED",
"CLOSED"
]
},
If applicable, reasons why alternative solutions are not sufficient:
The only way to disable "Notify on incident closure" is by doing it manually. If you manage Alert Policies by Terraform and change for example threshold value, that flag will be overwritten and you have to deselect this option again.
Other information (workarounds you have tried, documentation consulted, etc):