There is very useful integration between vRealize Operations, Log Insight, and vCenter Server. The products can be tied to each other to make them more seamless and easier to navigate. A few roles are required to be created to restrict permissions. I have the broad steps and links to the VMware articles below that detail the specific permissions and documentation. Go through the steps and then you will be able to launch in context.

As defined by VMware; launch in context is a feature in vROps that lets you launch an external application via URL in a specific context. The context is defined by the active UI element and object selection. Launch in context lets the Log Insight adapter add menu items to a number of different views within the Custom user interface and the vSphere user interface of Operations Manager.

• Create an AD user account for Log Insight and vROps to be used to integrate with the applications
• Create roles in the vCenter Server with the appropriate permissions for Log Insight and vROps
• Assign the service accounts their respective roles at the global permission level
• Create a role in vROPs with the appropriate permissions
• Connect vROps to a vCenter Server
• Connect Log Insight to a vCenter Server
  • All ESXi hosts in the vCenter Server can be selected to be added to Log Insight
• Connect vROps to Log Insight
• Connect Log Insight to vROps
  • Ran into two bugs – https://kb.vmware.com/s/article/2096520
    • When using AD account
    • Test failed: Invalid username or password – even though user name and password were definitely correct
    • Bug was supposed to be fixed in Log Insight v4.8. I reported it to VMware GSS.
    • Second problem was it did not work with vROps’s hostname
  • I created a local vROps account and used the IP address to make it work