Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com> #2
Hello, just to complement, we are using Akamai CDN and we are trying to get the customer IP on the GCP External Load Balancer via X-Forwarded-For, but it is not possible to get the info in the logs
jo...@jhanley.com <jo...@jhanley.com> #3
I am opposed to being able to modify Cloud Logging log entries. Log entries provide critical security and history information. I cannot see a scenario where that should be allowed or supported.
If you require this feature, export the logs to another logging or data storage system and process each entry as you require.
If you require this feature, export the logs to another logging or data storage system and process each entry as you require.
to...@cs.corpnet.pl <to...@cs.corpnet.pl> #4
Hello, I am very much in favor of a mechanism that will allow for efficient management of the severity with which a given log will be saved. Currently, it turns out that a lot of logs are incorrectly marked with the default treatment by logging mechanisms.
Such "new" mechanism that would allow us to consciously implement patterns for specific logs that impose the correct severity, and instead of information noise we would have valuable information.
Such "new" mechanism that would allow us to consciously implement patterns for specific logs that impose the correct severity, and instead of information noise we would have valuable information.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Being able to change the severity of all the Logs inside the Google Cloud Logging.
How this might work:
Being able to change the severity of all the logs google managed or not.
If applicable, reasons why alternative solutions are not sufficient:
No workarounds available.