{ "id": "VMwarevCenter", "title": "[Deprecated] VMware vCenter", "publisher": "VMware", "descriptionMarkdown": "The [vCenter](https://www.vmware.com/in/products/vcenter-server.html) connector allows you to easily connect your vCenter server logs with Microsoft Sentinel. This gives you more insight into your organization's data centers and improves your security operation capabilities.", "additionalRequirementBanner": "These queries are dependent on a parser based on a Kusto Function deployed as part of the solution.", "graphQueries": [ { "metricName": "Total data received", "legend": "vCenter", "baseQuery": "vCenter" } ], "sampleQueries": [ { "description": "Total Events by Event Type", "query": "vCenter \n | summarize count() by EventType" }, { "description": "log in/out to vCenter Server", "query": "vCenter \n | where EventType in ('UserLogoutSessionEvent','UserLoginSessionEvent') \n | summarize count() by EventType,EventID,UserName,UserAgent \n | top 10 by count_" } ], "dataTypes": [ { "name": "vcenter_CL", "lastDataReceivedQuery": "vCenter \n | summarize Time = max(TimeGenerated)\n | where isnotempty(Time)" } ], "connectivityCriterias": [ { "type": "IsConnectedQuery", "value": [ "vCenter \n | summarize LastLogReceived = max(TimeGenerated)\n | project IsConnected = LastLogReceived > ago(7d)" ] } ], "availability": { "status": 1, "isPreview": true }, "permissions": { "resourceProvider": [ { "provider": "Microsoft.OperationalInsights/workspaces", "permissionsDisplayText": "read and write permissions are required.", "providerDisplayName": "Workspace", "scope": "Workspace", "requiredPermissions": { "write": true, "read": true, "delete": true } }, { "provider": "Microsoft.OperationalInsights/workspaces/sharedKeys", "permissionsDisplayText": "read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).", "providerDisplayName": "Keys", "scope": "Workspace", "requiredPermissions": { "action": true } } ], "customs": [ { "name": "Include custom pre-requisites if the connectivity requires - else delete customs", "description": "Description for any custom pre-requisite" } ] }, "instructionSteps": [ { "title": "", "description": "**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias VMware vCenter and load the function code or click [here](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/VMware%20vCenter/Parsers/vCenter.txt), on the second line of the query, enter the hostname(s) of your VMware vCenter device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update. \n> 1. If you have not installed the vCenter solution from ContentHub then [Follow the steps](https://aka.ms/sentinel-vCenter-parser) to use the Kusto function alias, **vCenter**", "instructions": [] }, { "title": "1. Install and onboard the agent for Linux", "description": "Typically, you should install the agent on a different computer from the one on which the logs are generated.\n\n> Syslog logs are collected only from **Linux** agents.", "instructions": [ { "parameters": { "title": "Choose where to install the agent:", "instructionSteps": [ { "title": "Install agent on Azure Linux Virtual Machine", "description": "Select the machine to install the agent on and then click **Connect**.", "instructions": [ { "parameters": { "linkType": "InstallAgentOnLinuxVirtualMachine" }, "type": "InstallAgent" } ] }, { "title": "Install agent on a non-Azure Linux Machine", "description": "Download the agent on the relevant machine and follow the instructions.", "instructions": [ { "parameters": { "linkType": "InstallAgentOnLinuxNonAzure" }, "type": "InstallAgent" } ] } ] }, "type": "InstructionStepsGroup" } ] }, { "title": "2. Configure the logs to be collected", "description": "Follow the configuration steps below to get vCenter server logs into Microsoft Sentinel. Refer to the [Azure Monitor Documentation](https://docs.microsoft.com/azure/azure-monitor/agents/data-sources-json) for more details on these steps.\n For vCenter Server logs, we have issues while parsing the data by OMS agent data using default settings. \nSo we advice to capture the logs into custom table **vcenter_CL** using below instructions. \n1. Login to the server where you have installed OMS agent.\n2. Download config file vCenter.conf \n\t\twget -v https://aka.ms/sentinel-vcenteroms-conf -O vcenter.conf \n3. Copy vcenter.conf to the /etc/opt/microsoft/omsagent/**workspace_id**/conf/omsagent.d/ folder. \n\t\tcp vcenter.conf /etc/opt/microsoft/omsagent/<>/conf/omsagent.d/\n4. Edit vcenter.conf as follows:\n\n\t a. vcenter.conf uses the port **22033** by default. Ensure this port is not being used by any other source on your server\n\n\t b. If you would like to change the default port for **vcenter.conf** make sure that you dont use default Azure monotoring /log analytic agent ports I.e.(For example CEF uses TCP port **25226** or **25224**) \n\n\t c. replace **workspace_id** with real value of your Workspace ID (lines 13,14,15,18)\n5. Save changes and restart the Azure Log Analytics agent for Linux service with the following command:\n\t\tsudo /opt/microsoft/omsagent/bin/service_control restart\n6. Modify /etc/rsyslog.conf file - add below template preferably at the beginning / before directives section \n\n\t\t$template vcenter,\"%timestamp% %hostname% %msg%\\ n\" \n\n **Note - There is no space between slash(\\\\) and character 'n' in above command.**\n\n 7. Create a custom conf file in /etc/rsyslog.d/ for example 10-vcenter.conf and add following filter conditions.\n\nDownload config file [10-vCenter.conf](https://aka.ms/sentinel-vcenter-conf)\n\n\t With an added statement you will need to create a filter which will specify the logs coming from the vcenter server to be forwarded to the custom table.\n\n\t reference: [Filter Conditions — rsyslog 8.18.0.master documentation](https://rsyslog.readthedocs.io/en/latest/configuration/filters.html)\n\n\t Here is an example of filtering that can be defined, this is not complete and will require additional testing for each installation.\n\t\t if $rawmsg contains \"vcenter-server\" then @@127.0.0.1:22033;vcenter\n\t\t & stop \n\t\t if $rawmsg contains \"vpxd\" then @@127.0.0.1:22033;vcenter\n\t\t & stop\n\t\t \n8. Restart rsyslog\n\t\t systemctl restart rsyslog", "instructions": [ { "parameters": { "fillWith": [ "WorkspaceId" ], "label": "Workspace ID" }, "type": "CopyableLabel" } ] }, { "title": "3. Configure and connect the vCenter device(s)", "description": "[Follow these instructions](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-9633A961-A5C3-4658-B099-B81E0512DC21.html) to configure the vCenter to forward syslog. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address." } ], "metadata": { "id": "VMwarevCenter", "version": "1.0.0", "kind": "dataConnector", "source": { "kind": "solution", "name": "VMware vCenter" }, "author": { "name": "Microsoft" }, "support": { "tier": "microsoft", "name": "Microsoft", "email": "support@microsoft.com" } } }