Assigned
Status Update
Comments
nu...@google.com <nu...@google.com>
ra...@google.com <ra...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
ha...@google.com <ha...@google.com> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
Description
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.
Problem you have encountered: By using the “Cloud Logging agent” [1] (with the google-fluentd version 1.9.2) [2], and the systemd plugin [fluent-plugin-systemd 1.0.5] [3], you may see a steady increase in the [Google Fluentd Logging Agent memory usage] in your instance. This steady increase could be in the hundreds of MiB per week.
What you expected to happen: The memory usage of the “Cloud Logging agent” should have a relatively stable value (considering that there are no increases in the volume of logs).
Steps to reproduce: Review the memory usage (time series) of the [Google Fluentd Logging Agent] in the VM instance.
Other information (workarounds you have tried, documentation consulted, etc):
[Workarounds]
========
Reference:
[1]https://cloud.google.com/logging/docs/agent/logging
[2]https://github.com/GoogleCloudPlatform/google-fluentd/releases/tag/1.9.2
[3]https://github.com/fluent-plugin-systemd/fluent-plugin-systemd
[4]https://github.com/fluent/fluentd/issues/3401
[5]https://cloud.google.com/logging/docs/agent/logging/installation#restart
[6]https://cloud.google.com/logging/docs/agent
[7]https://cloud.google.com/logging/docs/agent/ops-agent