Assigned
Status Update
No update yet.
Comments
se...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
[Deleted User] <[Deleted User]>
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.
bo...@gmail.com
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.
ti...@narative.io
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
bo...@gmail.com
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
am...@indihood.com
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
sh...@gmail.com
+1 to the last commenter. First, you have some OS that does not support your ops-agent, and I want to raise an alert on it, at least programmatically.
sa...@google.com
sa...@google.com
[Deleted User] <[Deleted User]>
+1 for feature request. It's important to create informational and useful messages.
ha...@instruqt.com
+1
Mi...@VUMC.org
+1
na...@blacklocus.com
+1
ri...@addition.ml
+1
c....@cue-health.me
+1
si...@tembici.com
+1
su...@gmail.com
+1
ig...@gmail.com
+1
at...@zozo.com
+1
ma...@gendigital.com
+1
y2...@heb.com
+1
an...@airfrance.fr
+1
da...@bilt.com
+1
to...@endava.com
+1 - Any news or progress on this?
bb...@alloprof.qc.ca
+1
si...@finnomena.com
+1
io...@recup.de
+1
rg...@screenly.io
+1
in...@wellsfargo.com Restricted+
Restricted+
Comment has been deleted.
da...@eagleeye.com
We create alerts using Terraform and the code differs slightly to the one provided by Google GUI, as a result I would like manually trigger a test alert to ensure that the Documentation field is populated with labels as expected.
This issue impacts us.
This issue impacts us.
ch...@gmail.com
+1
kr...@cloudoffice.bg
3 years later xD
af...@league.com
+1
d....@hbm-machines.com
+1
di...@metro.digital
+1
se...@ingka.ikea.com
+1
an...@ingka.ikea.com
+1
en...@ingka.ikea.com
This is really needed, we want to be able to automatically test if notification channels are in fact still working, e.g. after token rotation.
is...@anz.com
Really quite ridiculous that this doesn't exist as a feature.
ke...@sada.com
+1 we need this feature.
hi...@xebia.com
I hope this feature will be implemented with gcloud command first. That's usually the easier method to get new features out using the gcloud alpha commands.
il...@airteam.ai
+1
jb...@gannett.com
any update on this?
no...@nytimes.com
+1
Description
I would like to manually trigger alert for alert policy for testing the notification. Will mainly help in conducting dry runs with incident management systems like Opsgenie
How this might work:
Provide an option from UI for each alert policy to trigger an alert. In the alert details, it could be indicated that this is a test alert
If applicable, reasons why alternative solutions are not sufficient:
Alternative are cumbersome. These include
1. Setting the thresholds such that the alert is triggered. This is hard to replicate for all scenarios. For e.g. absence of a metric
2. Manually creating time series which will trigger the alerts. Lot of work for just testing the notifications
Other information (workarounds you have tried, documentation consulted, etc):