Skip to content

Commit 77bc7ca

Browse files
authored
Merge pull request #100119 from dlepow/acifresh9
[ACI Freshness] ACI resource logs
2 parents adab919 + 36b792c commit 77bc7ca

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/container-instances/container-instances-log-analytics.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Resource logs for container groups
2+
title: Collect & analyze resource logs
33
description: Learn how to send resource logs and event data from container groups in Azure Container Instances to Azure Monitor logs
44
ms.topic: article
5-
ms.date: 09/02/2019
5+
ms.date: 01/08/2020
66
ms.author: danlep
77
---
88
# Container group and instance logging with Azure Monitor logs
99

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.
1111

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.
1313

1414
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]
1515

@@ -40,7 +40,7 @@ To obtain the log analytics workspace ID and primary key:
4040

4141
Now that you have the log analytics workspace ID and primary key, you're ready to create a logging-enabled container group.
4242

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.
4444

4545
### Deploy with Azure CLI
4646

@@ -124,7 +124,7 @@ Azure Monitor logs includes an extensive [query language][query_lang] for pullin
124124

125125
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.
126126

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":
128128

129129
```query
130130
ContainerInstanceLog_CL

0 commit comments

Comments
 (0)