I noticed vRA and vRO have their VRLI agent set to not configurable, why is a VRLI agent group created from Linux - Systemd when it can't modify the configuration of the agent on vRA and vRO? Is VCF changing the agent to configurable in the background?
Assuming VCF 4.1 and later, If vRealize Automation is deployed in "vcf-mode" from a vRSLCM instance managed by SDDC Manager and where vRealize Log Insight is already deployed and managed, then vRealize Automation is automatically configured to send logs to vRealize Log Insight Cluster over TCP 9000 - essentially it uses the "vracli vrli set" to configure Fluentd to send the logs over the unencrypted path.
You can use the PowerValidatedSolutions module to return the status of the configuration or set it, too, after deployment.
The step I was looking at is when you create the Agent Group from Linux - Systemd in vRLI, when you add vRA or vRO it says the agent can't be configured. In /etc/liagent.ini global_config is set to no not allowing the content pack customization to the agent config on the monitored appliance.
Ah, gotcha. Yes, it does look like an issue based on a testbed I just looked at moments ago.
Please login to docs.vmware.com using VMware Customer Connect and use the Send Feedback option. This will open a documentation issue for this VMware Validated Solution that myself and our team will review.
Just sent feedback, thanks. I'll wait to see what we should be doing, I'm guessing a new empty group that has no configuration so that the appliances are still grouped together for easy viewing.