|
1 | 1 | ---
|
2 |
| -title: Resource logs for container groups |
| 2 | +title: Collect & analyze resource logs |
3 | 3 | description: Learn how to send resource logs and event data from container groups in Azure Container Instances to Azure Monitor logs
|
4 | 4 | ms.topic: article
|
5 |
| -ms.date: 09/02/2019 |
| 5 | +ms.date: 01/08/2020 |
6 | 6 | ms.author: danlep
|
7 | 7 | ---
|
8 | 8 | # Container group and instance logging with Azure Monitor logs
|
9 | 9 |
|
10 |
| -Log Analytics workspaces provide a centralized location for storing and querying log data from not only Azure resources, but also on-premises resources and resources in other clouds. Azure Container Instances includes built-in support for sending logs and event data to Azure Monitor logs. |
| 10 | +Log Analytics workspaces provide a centralized location for storing and querying log data not only from Azure resources, but also on-premises resources and resources in other clouds. Azure Container Instances includes built-in support for sending logs and event data to Azure Monitor logs. |
11 | 11 |
|
12 |
| -To send container group log and event data to Azure Monitor logs, you must specify a Log Analytics workspace ID and workspace key when creating a container group. The following sections describe creating a logging-enabled container group and querying logs. |
| 12 | +To send container group log and event data to Azure Monitor logs, specify an existing Log Analytics workspace ID and workspace key when creating a container group. The following sections describe how to create a logging-enabled container group and how to query logs. |
13 | 13 |
|
14 | 14 | [!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]
|
15 | 15 |
|
@@ -40,7 +40,7 @@ To obtain the log analytics workspace ID and primary key:
|
40 | 40 |
|
41 | 41 | Now that you have the log analytics workspace ID and primary key, you're ready to create a logging-enabled container group.
|
42 | 42 |
|
43 |
| -The following examples demonstrate two ways to create a container group with a single [fluentd][fluentd] container: Azure CLI, and Azure CLI with a YAML template. The Fluentd container produces several lines of output in its default configuration. Because this output is sent to your Log Analytics workspace, it works well for demonstrating the viewing and querying of logs. |
| 43 | +The following examples demonstrate two ways to create a container group that consists of a single [fluentd][fluentd] container: Azure CLI, and Azure CLI with a YAML template. The fluentd container produces several lines of output in its default configuration. Because this output is sent to your Log Analytics workspace, it works well for demonstrating the viewing and querying of logs. |
44 | 44 |
|
45 | 45 | ### Deploy with Azure CLI
|
46 | 46 |
|
@@ -124,7 +124,7 @@ Azure Monitor logs includes an extensive [query language][query_lang] for pullin
|
124 | 124 |
|
125 | 125 | The basic structure of a query is the source table (in this article, `ContainerInstanceLog_CL` or `ContainerEvent_CL`) followed by a series of operators separated by the pipe character (`|`). You can chain several operators to refine the results and perform advanced functions.
|
126 | 126 |
|
127 |
| -To see example query results, paste the following query into the query text box , and select the **Run** button to execute the query. This query displays all log entries whose "Message" field contains the word "warn": |
| 127 | +To see example query results, paste the following query into the query text box, and select the **Run** button to execute the query. This query displays all log entries whose "Message" field contains the word "warn": |
128 | 128 |
|
129 | 129 | ```query
|
130 | 130 | ContainerInstanceLog_CL
|
|
0 commit comments