Assigned
Status Update
Comments
ti...@google.com <ti...@google.com>
sa...@google.com <sa...@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
ch...@cmegroup.com <ch...@cmegroup.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
Issue summary: Some customers are requesting that our Cloud Ops Agent should allow for multiple file configurations, like our Legacy Logging Agent did.
Customer expectation for this feature is to be able to add multiple configuration files in one path so they're able to abstract single configuration files for their separate needs (file for OS logging, file for custom application logging).
In our Legacy Logging agent, if you added multiple configuration files into "/etc/google-fluentd/config.d/" folder, it'd use all the files and its configuration. Meanwhile, in our Ops Agent, you're only allowed to define configuration for the logging agent in the "/etc/google-cloud-ops-agent/config.yaml" file.