There is a difference between "works" and "supported". Yes to the former and no to the latter unless you get an RPQ from VMware.
Yes I installed the Agent into a POC environment and it seems to work.
daphnissov, is there any official documentation from VMware on this?
Not when it comes to installing it on other VMware appliances.
So where did you pull "works" and "supported" from?
"Works" because, well, it works. (Not) "Supported" because it is not supported to install *any* foreign software on VMware appliances.
So would this answer be sufficient to the Director at my company;
The 'Download Log Insight Agent Version 4.5.0' link from the Log Insight Appliance *only* applies to a Windows OS *OR* a Linux OS, where you wish to gather logs more robustly.
The Linux RPM, DEB or BIN *should not* be installed on *any* VA distributed by VMware. vROps, vRA, vCSA, etc.
To configure the Log Insight Agent for a VMware Appliance (vROps, vRA, vCSA, etc.). Please use the built in liagent.ini *if* it is there. If not, tough.
Yep, that's about the sum of it. The only VMware appliances I know of that ship with the Log Insight agent today are vRO, vRA, vROps, and vRBC. vCSA does not ship with the vRLI agent.
One more query. It's related to vROps Agent configuration where vROps is spread across 2 sites.
My question is where do I point the vROps Analystics Cluster Nodes? For example, I have a vROps Cluster deployed across Sites 1 & 2. Do I point each vROps node to the Log Insight Cluster at the same site?
Site 1 - Log Insight Cluster 1, vROps Master Node, Master Replica, Data Nodes, Remote Collector 1
Site 2 - Log Insight Cluster 2, Remote Collector 2
So from the design above, would it look like the following?
Point to Log Insight at Site 1: vROps Master Node, Master Replica, Data Nodes, Remote Collector 1
Point to Log Insight at Site 1: Remote Collector 2
Your remote collector, although in Site 2, belongs to the deployment hosted in Site 1. Therefore, I'd point the log stream of that collector to the vRLI cluster in Site 1.