Assigned
Status Update
No update yet.
Comments
jh...@google.com
jp...@gmail.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
fe...@nbx.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.
jn...@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.
aa...@gmail.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
[Deleted User] <[Deleted User]>
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
ro...@bird.com
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
br...@intigriti.com
+1
kw...@utah.gov
+1
ma...@gmail.com
+1
[Deleted User] <[Deleted User]>
+1
[Deleted User] <[Deleted User]>
+1
jo...@nandos.co.uk
+1
ss...@squarespace.com
+1
ik...@symphony.com
+1
jo...@openrm.co.jp
+1
[Deleted User] <[Deleted User]>
+1
se...@gmail.com
+1
an...@meditab.com
+1
se...@aeros.la
+1
[Deleted User] <[Deleted User]>
+1
ed...@accenture.com
+1
la...@camus.energy
Comment has been deleted.
ak...@dac.co.jp
+1
st...@puzzle.ch
+1
je...@metalgear.xyz
+1
bf...@benchsci.com
+1
ca...@wilmaa.com
+1
jo...@awellhealth.com
+1
ba...@google.com
dh...@google.com
sa...@db.com
Add type conversions, please!
dh...@google.com
ds...@gmail.com
+1
bd...@loblaw.ca
+1
s....@reply.it
+1
st...@sky.uk
+1
ha...@joincandidhealth.com
+1
ni...@whirlpool.com
+1
ha...@helloprint.com
+1
le...@luizalabs.com
Comment has been deleted.
Description
Use jsonPayload.bytes_sent with > and < to get the "lower than" and the "bigger than" logs filtered.
How this might work:
Example:
jsonPayload.bytes_sent>="100" to get the logs that have 100 or more bytes_sent.
jsonPayload.bytes_sent<="100" to get the logs that have 100 or less bytes_sent.
If applicable, reasons why alternative solutions are not sufficient:
At this moment the advanced filter with jsonPayload.bytes_sent only works for showing matching entries or hiding matching entries ( = and != ).