This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 307
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make paths relative rather than absolute for linkages
- Loading branch information
Showing
3 changed files
with
30 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -21,7 +21,7 @@ And one of: | |
| * CentOS 7 | ||
| * SUSE Linux Enterprise Server 12 | ||
|
|
||
| You'll need to [install the OMS Agent for Linux] (https://github.com/MSFTOSSMgmt/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md#steps-to-install-the-oms-agent-for-linux) on each host and then do the following to configure your containers to use the FluentD logging driver: | ||
| You'll need to [install the OMS Agent for Linux] (docs/OMS-Agent-for-Linux.md#steps-to-install-the-oms-agent-for-linux) on each host and then do the following to configure your containers to use the FluentD logging driver: | ||
|
|
||
| * Edit `/etc/default/docker` and add this line: | ||
| ``` | ||
|
|
@@ -39,7 +39,7 @@ Once you’re set up, we’d like you to try the following scenarios and play ar | |
| ### Overview | ||
| Look at the Container top tile – it’s intended to show you a quick overview of the system. Does it contain the information you need to see first? If not, tell us what you expect to see instead. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| The top tile shows hosts that are overwhelmed with CPU or Memory usage (>90%), as well as an overview of how many containers you have in the environment and whether they’re failed, running, or stopped. | ||
|
|
||
|
|
@@ -52,11 +52,11 @@ Click the solution pack tile. From there you’ll see views organized by: | |
| The container solutions pack works by collecting various performance metrics and log data and sending it to the Operations Management Suite service. Each pane you see on the UI is a visual representation of a search that is run on this data. | ||
|
|
||
| **Try it:** Click on the top tile of this pane. | ||
|  | ||
|  | ||
|
|
||
| You should see something like this: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| 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://technet.microsoft.com/library/mt484120.aspx). | ||
|
|
||
|
|
@@ -65,23 +65,23 @@ From here you can edit the search query to modify it to something specific. For | |
| ### Finding a failed container | ||
| OMS will mark a container as Failed if it has exited with a non-zero exit code. You can see an overview of the errors and failures in the environment in this tile: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| **Try it:** Get specifics of a failed container by clicking on the tile. You’ll see something like this: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| From here, click on one of the image names to get additional information such as image size and number of stopped and failed images. Expand the “show more” to get the image ID: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| **Try it:** Find the container that is running this image. Type the following into the search box: | ||
| ``` | ||
| Type=ContainerInventory <ImageID> | ||
| ``` | ||
| This will show you the logs and you can scroll to see the failed container: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ### Search Logs | ||
| When you’re troubleshooting a specific error, it can help to see where it is occurring in your environment. Become familiar with the types of logs so you can construct queries to get the information you want: | ||
|
|
@@ -97,7 +97,7 @@ When you’re troubleshooting a specific error, it can help to see where it is o | |
| Type=ContainerInventory drupal Failed | ||
| ``` | ||
|
|
||
|  | ||
|  | ||
|
|
||
| Note the name of the container under “Name”, and do a search for those logs. In our case, it would be `Type=ContainerLog prickly_varahamihira.` | ||
|
|
||
|
|
@@ -107,31 +107,31 @@ When you’re beginning to construct queries, it can help to see what’s possib | |
| Type=Perf * | ||
| ``` | ||
|
|
||
|  | ||
|  | ||
|
|
||
| You can see this in a more graphical form if you click the word “Metrics” on the upper right: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| **Try it:** Scope the performance data you’re seeing to a specific container by adding typing the name of it to the right of your query: | ||
| ``` | ||
| Type=Perf <containerName> | ||
| ``` | ||
|
|
||
|  | ||
|  | ||
|
|
||
| Scroll around to see the list of which performance metrics are collected for an individual container. | ||
|
|
||
| ## Example queries | ||
| Finally, sometimes it can help to build queries by beginning with an example or two and adjusting to fit your environment. Play around with the links on the Notable Queries page (on the far right) to help you build more advanced queries: | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ## Saving queries | ||
| Saving queries is a standard feature in OMS and can help you keep queries you’ve found useful. | ||
|
|
||
| **Try it:** After you construct a query you find useful, save it by clicking the star at the bottom. This will let you easily access it later from the My Dashboard page. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| If you’ve made it this far, thanks a bunch. Drop us a line at [email protected] and let us know you made it through – tell us what works, what doesn’t, and what we need to build next. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters