Update public preview for VMware

microsoft · Sep 21, 2016 · 0e6bc2a · 0e6bc2a
1 parent 1f1d245
commit 0e6bc2a
Show file tree

Hide file tree

Showing 10 changed files with 28 additions and 30 deletions.
diff --git a/docs/VMware-Instruction.md b/docs/VMware-Instruction.md
@@ -1,30 +1,28 @@
-# Trying the VMWare Log Monitoring Solution for Operations Management Suite
+# Trying the VMware Monitoring Solution for Operations Management Suite
 
- VMWare logs can be massive in scale and difficult to capture and manage. In order to do troubleshooting and alerting using deep log analysis and trends, a centralized approach for logging and monitoring is required.  
+ VMware logs can be massive in scale and difficult to capture and manage. In order to do troubleshooting and alerting using deep log analysis and trends, a centralized approach for logging and monitoring is required.  
 
-### What can you do with the VMWare Log Monitoring Solution?  
- - See information about all VMWare ESXi Hosts in a single location 
+### What can you do with the VMware Monitoring Solution?  
+ - See information about all VMware ESXi Hosts in a single location 
  - Know what the top event counts, status, and trends of VM and ESXi Hosts provided thru the ESXi Host logs 
  - Troubleshoot by viewing and searching centralized logs of ESXi Hosts.  
  - Provide alerting based on the log search queries  
 
-#### Supported VMWare ESXi Host:  
+#### Supported VMware ESXi Host:  
   vSphere ESXi Host 5.5, 6.0 
 
-#### How do I set up the VMWare Solution?  
+#### How do I set up the VMware Monitoring Solution?  
    First, you will need to create a Linux OS VM to receive all syslog from the ESXi Hosts. The OMS Linux Agent will be the collecting point for all ESXi Host syslog. You can have multiple ESXi Hosts forwarding logs to a single linux server as you see in the diagram below.  
 
-   ![diagram](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/diagram.png?raw=true)
-
-This is a Private Preview product. If you would like to participate in Private Preview program, please contact OMSVMWare@microsoft.com. We will enable you. Please try out some scenarios we have and give us any feedback. We love to hear from you.
+   ![diagram](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/diagram.png?raw=true)
 
 ### Here are the steps to set up the syslog collection for ESXi Host and OMS Linux Agent installation:
 
 1. Setup syslog forwarding for VSphere. For detailed steps that set up syslog forwarding on ESXi Host, see [Configuring syslog on ESXi 5.x and 6.0 (2003322)](https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003322).
 
     Go to **ESXi Host Configuration -> Software/Advanced Settings -> Syslog**
 
-![vsphereconfig](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/vsphere1.png?raw=true)
+![vsphereconfig](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/vsphere1.png?raw=true)
 
 In the *Syslog.global.logHost* field, add your linux server and the port number *1514*. 
 
@@ -33,9 +31,9 @@ In the *Syslog.global.logHost* field, add your linux server and the port number
 2.	Make sure to open the ESXi Host firewall for syslog. 
   Go to **ESXi Host Configuration -> Software/Security Profile-> Firewall** and open properties. 
 
-![vspherefw](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/vsphere2.png?raw=true)
+![vspherefw](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/vsphere2.png?raw=true)
 
-![vspherefwproperties](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/vsphere3.png?raw=true)
+![vspherefwproperties](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/vsphere3.png?raw=true)
 
 Check the vSphere Console to see whether the syslog is properly set up. Confirm from the ESXI Host that it shows that port **1514** is configured. 
 
@@ -57,70 +55,70 @@ Connection to 123.456.789.101 1514 port [tcp/*] succeeded!
 `Type=VMware_CL`
 
 
-![type](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/type.png?raw=true)
+![type](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/type.png?raw=true)
 
-If you can see this, you are all set for the OMS VMWare Solution Dashboard.  
+If you can see this, you are all set for the OMS VMware Solution Dashboard.  
 
 
-## VMWare Solution on OMS 
-Once you’ve enabled VMWare Solution and have set up the OMS Agent for Linux, you are ready for the VMWare Solution. 
+## VMware Solution on OMS 
+Once you’ve enabled VMware Solution and have set up the OMS Agent for Linux, you are ready for the VMware Solution. 
 
-### VMWare Solution Overview
-When you open the OMS web portal, you will see an overview tile called VMWare. It will provide you a quick high level view of the failures stated on OMS. Once you click on this overview tile, you go into a dashboard view. 
+### VMware Solution Overview
+When you open the OMS web portal, you will see an overview tile called VMware. It will provide you a quick high level view of the failures stated on OMS. Once you click on this overview tile, you go into a dashboard view. 
 
-![tile](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/tile.PNG?raw=true)
+![tile](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/tile.PNG?raw=true)
 
 #### Navigating the Dashboard view
-Once you’ve clicked on the VMWare Solution tile, you will see the views organized by: 
+Once you’ve clicked on the VMware Solution tile, you will see the views organized by: 
 - Failure Status Count
 - Top Host by Event Counts
 - Top Event Counts
 - Virtual Machine Activities
 - ESXi Host Disk Events
 
 
-![solution1](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/SolutionView1-1.PNG?raw=true)
+![solution1](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/SolutionView1-1.PNG?raw=true)
 
-![solution2](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/SolutionView1-2.PNG?raw=true)
+![solution2](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/SolutionView1-2.PNG?raw=true)
 
 Click on any tile and this will take you to the Log Analytics Search pane. This will provide you more detailed information. 
 
 From here you can edit the search query to modify it to something specific. For a tutorial on the basics of OMS search, check out the [OMS log search tutorial.](https://azure.microsoft.com/documentation/articles/log-analytics-log-searches/)
 
 #### Finding ESXi Host’s Top Events and ESXi Host with high event counts
-A single ESXi Host will generate multiple logs based on their processes. The OMS VMWare Solution centralizes this and summarizes the event counts. This way, you can understand which ESXi Host has a high volume of events and what events are toping in the environment. 
+A single ESXi Host will generate multiple logs based on their processes. The OMS VMware Solution centralizes this and summarizes the event counts. This way, you can understand which ESXi Host has a high volume of events and what events are toping in the environment. 
 
-![event](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/Events.PNG?raw=true)
+![event](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/Events.PNG?raw=true)
 
 You can drill down further by either clicking in the ESXi Host or Event Type. 
 
 If you selected the ESXi Host name, you will view information from that ESXi Host. If you would like to narrow further with the Event Type, you can add **“ProcessName_s=EVENT TYPE”** in your search query. Of course, you can select the ProcessName from the search filter on the left-hand side.  This will narrow the information for you. 
 
 
-![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/eventhostdrilldown.PNG?raw=true)
+![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/eventhostdrilldown.PNG?raw=true)
 
 #### Finding ESXi Host with high VM creation or deletion activities
 A Virtual Machine (VM) can be created and deleted on any ESXi Host. For an administrator to understand which ESXi Host has how many VMs creates, this will be helpful to understand performance and capacity planning. Keeping track of the VM activity events is crucial when managing the environment. 
 
-![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/VM%20Activities1.PNG?raw=true)
+![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/VM%20Activities1.PNG?raw=true)
 
 If you want to see additional ESXi Host VM creation information, click on the ESXi Host name and you will see more information. 
 
-![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/CreateVM.PNG?raw=true)
+![drill](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/CreateVM.PNG?raw=true)
 
 #### Other queries 
 We’ve provided some queries which can be used such as disk space full, storage latency, path failure, and more. 
 
-![queries](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/VMwarePics/Queries.PNG?raw=true)
+![queries](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/VMwarePics/Queries.PNG?raw=true)
 
 #### Saving queries
 Saving queries is a standard feature in OMS and can help you keep queries you’ve found useful. 
 After you construct a query you find useful, save it by clicking the star at the top. This will let you easily access it later from the My Dashboard page.
 
-![DockerDashboardView](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/keikodoc/docs/pictures/DockerPics/DockerDashboardView.png?raw=true)
+![DockerDashboardView](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/pictures/DockerPics/DockerDashboardView.png?raw=true)
 
 #### Alerting using queries
 Once you’ve created your queries, you may want to use the queries to alert you on events. For more information on how to set up alerting, please refer to documentation on Alerts in Log Analytics. 
-Also, I’ve also posted a blog with some examples of the alerting queries and other query examples. Please refer to Monitor VMWare using OMS Log Analytics blog. 
+Also, I’ve also posted a blog with some examples of the alerting queries and other query examples. Please refer to Monitor VMware using OMS Log Analytics blog. 
 
 If you have any questions or suggestions, please contact OMSVMWare@microsoft.com. We love to hear from you. 
diff --git a/docs/pictures/VMwarePics/CreateVM.PNG b/docs/pictures/VMwarePics/CreateVM.PNG
diff --git a/docs/pictures/VMwarePics/Events.PNG b/docs/pictures/VMwarePics/Events.PNG
diff --git a/docs/pictures/VMwarePics/Queries.PNG b/docs/pictures/VMwarePics/Queries.PNG
diff --git a/docs/pictures/VMwarePics/SolutionView1-1.PNG b/docs/pictures/VMwarePics/SolutionView1-1.PNG
diff --git a/docs/pictures/VMwarePics/SolutionView1-2.PNG b/docs/pictures/VMwarePics/SolutionView1-2.PNG
diff --git a/docs/pictures/VMwarePics/VM Activities1.PNG b/docs/pictures/VMwarePics/VM Activities1.PNG
diff --git a/docs/pictures/VMwarePics/diagram.png b/docs/pictures/VMwarePics/diagram.png
diff --git a/docs/pictures/VMwarePics/eventhostdrilldown.PNG b/docs/pictures/VMwarePics/eventhostdrilldown.PNG
diff --git a/docs/pictures/VMwarePics/type.png b/docs/pictures/VMwarePics/type.png