Configure a log sink/export to pubsub to use an ordering key [171971952]

Assigned

Feature Request

Status Update

No update yet.

Description

ah...@google.com

created issue #1

Oct 29, 2020 03:51PM

This will create a public issue which anybody can view and comment on.

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.

We want Cloud Logging Sink to Pub/Sub feature [1] to have an option in Cloud Logging to allow you to set the 'orderingKey' [2] Pub/Sub message attribute for every log it sends to Pub/Sub. For example, set 'orderingKey' to the timestamp of the log.

[1]

https://cloud.google.com/logging/docs/export/configure_export_v2#exporting_logs
[2]

https://cloud.google.com/pubsub/docs/reference/rest/v1/PubsubMessage

Other information (workarounds you have tried, documentation consulted, etc):

The workaround could be to have the Subscriber client manually parse the log JSON it receives, to manually find a specific value for ordering (like the log timestamp for example).

Comments

ah...@google.com <ah...@google.com> Oct 29, 2020 03:51PM

Assigned to gc...@google.com.

[Deleted User] <[Deleted User]> #2Feb 19, 2021 03:20AM

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.

ra...@wpengine.com <ra...@wpengine.com> #3Jul 1, 2021 08:15AM

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.

pa...@pingidentity.com <pa...@pingidentity.com> #4Feb 4, 2022 09:15PM

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.

ar...@seclogic.io <ar...@seclogic.io> #5Sep 26, 2022 12:19PM

Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?

ja...@imperva.com <ja...@imperva.com> #6May 17, 2023 04:34PM

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

be...@imperva.com <be...@imperva.com> #7May 17, 2023 04:48PM

Hi ,

Can somebody tell the exact metric for memory based autoscaling

be...@imperva.com <be...@imperva.com> #8Jun 6, 2023 07:59PM

Any news on an ETA for this fix?

ba...@google.com <ba...@google.com> Jun 7, 2023 12:11AM

Reassigned to ba...@google.com.

ba...@google.com <ba...@google.com> #9Jun 7, 2023 04:22AM

Reassigned to gc...@google.com.

Hello,

Thanks for reaching out to us!

The Product Engineering Team has been made aware of this feature request. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Any further updates will be communicated here in this thread. Thank you for your trust and continued support to improve Google Cloud Platform products.

In case you want to report a new issue, please do not hesitate to create a new Issue Tracker thread describing your issue. Once again, thank you for the suggestions.

Thanks & Regards,
Manish Bavireddy.
Google Cloud Support