You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-signalr/monitor-signalr.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,7 +127,6 @@ For example Kusto queries for Azure SignalR Service, see [Queries for the Signal
127
127
> [!NOTE]
128
128
> Query field names for Storage destinations differ slightly from field names for Log Analytics. For details about the field name mappings between Storage and Log Analytics tables, see [Resource Log table mapping](monitor-signalr-reference.md#resource-log-table-mapping).
See [Monitor Container Instances](monitor-azure-container-instances.md) for details on the data you can collect for Container Instances and how to use it.
|**containerName**| The name of the container. The name must be between 1 and 63 characters long. It can contain only lowercase letters numbers, and dashes. Dashes can't begin or end the name, and dashes can't be consecutive. The name must be unique in its resource group. |
Container Instances has two table schemas, a legacy schema for Log Analytics and a new schema that supports diagnostic settings. Diagnostic settings is in public preview in the Azure portal. You can use either or both schemas at the same time.
The following table lists a subset of the operations that Azure Container Instances may record in the Activity log. For the complete listing, see [Microsoft.ContainerInstance resource provider operations](/azure/role-based-access-control/resource-provider-operations#microsoftcontainerinstance).
For more information about the resource types for Azure Container Instances, see [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md).
20
18
21
-
<!-- ## Data storage. Required section. Optionally, add service-specific information about storing your monitoring data after the include. -->
For a list of available metrics for Container Instances, see [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md#metrics).
@@ -32,27 +26,15 @@ All metrics for Container Instances are in the namespace **Container group stand
32
26
33
27
Containers generate similar data as other Azure resources, but they require a containerized agent to collect required data. For more information about container metrics for Container Instances, see [Monitor container resources in Azure Container Instances](container-instances-monitor.md).
34
28
35
-
<!-- METRICS SECTION END ------------------------------------->
- For more information about how to get log data for Container Instances, see [Retrieve container logs and events in Azure Container Instances](container-instances-get-logs.md).
43
32
- For the available resource log categories, associated Log Analytics tables, and the logs schemas for Container Instances, see [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md#resource-logs).
44
33
45
-
<!-- ## Activity log. Required section. Optionally, add service-specific information about your activity log after the include. -->
@@ -63,7 +45,6 @@ For detailed information and instructions for querying logs, see [Container grou
63
45
64
46
For the Azure Monitor logs table schemas for Container Instances, see [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md#azure-monitor-logs-tables).
65
47
66
-
<!-- ### Sample Kusto queries. Required section. If you have sample Kusto queries for your service, add them after the include. -->
The following query examples use the legacy Log Analytics log tables. The basic structure of a query is the source table, `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.
@@ -85,17 +66,10 @@ ContainerInstanceLog_CL
85
66
| where (TimeGenerated > ago(1h))
86
67
```
87
68
88
-
<!-- ANALYSIS SECTION END ------------------------------------->
The following table lists common and recommended alert rules for Container Instances.
101
75
@@ -105,11 +79,8 @@ The following table lists common and recommended alert rules for Container Insta
105
79
| Activity logs | Container Instances operations like create, update, and delete | See the [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md#activity-log) for a list of activities you can track. |
106
80
| Log alerts |`stdout` and `stderr` outputs in the logs | Use custom log search to set alerts for specific outputs that appear in logs. |
<!-- ALERTS SECTION END -------------------------------------->
112
-
113
84
## Related content
114
85
115
86
- See [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md) for a reference of the metrics, logs, and other important values created for Container Instances.
Copy file name to clipboardExpand all lines: articles/search/monitor-azure-cognitive-search-data-reference.md
+2-39Lines changed: 2 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,42 +9,14 @@ ms.author: heidist
9
9
ms.service: cognitive-search
10
10
---
11
11
12
-
<!--
13
-
IMPORTANT
14
-
To make this template easier to use, first:
15
-
1. Search and replace AI Search with the official name of your service.
16
-
2. Search and replace azure-cognitive-search with the service name to use in GitHub filenames.-->
17
-
18
-
<!-- VERSION 3.0 2024_01_01
19
-
For background about this template, see https://review.learn.microsoft.com/en-us/help/contribute/contribute-monitoring?branch=main -->
20
-
21
-
<!-- Most services can use the following sections unchanged. All headings are required unless otherwise noted.
22
-
The sections use #included text you don't have to maintain, which changes when Azure Monitor functionality changes. Add info into the designated service-specific places if necessary. Remove #includes or template content that aren't relevant to your service.
23
-
24
-
At a minimum your service should have the following two articles:
25
-
26
-
1. The primary monitoring article (based on the template monitor-service-template.md)
27
-
- Title: "Monitor AI Search"
28
-
- TOC title: "Monitor"
29
-
- Filename: "monitor-azure-cognitive-search.md"
30
-
31
-
2. A reference article that lists all the metrics and logs for your service (based on this template).
@@ -54,7 +26,6 @@ SearchQueriesPerSecond shows the average of the search queries per second (QPS)
54
26
55
27
For example, within one minute, you might have a pattern like this: one second of high load that is the maximum for SearchQueriesPerSecond, followed by 58 seconds of average load, and finally one second with only one query, which is the minimum.
Azure AI Search has the following dimensions associated with the metrics that capture a count of documents or skills that were executed, "Document processed count" and "Skill execution invocation count".
@@ -69,16 +40,13 @@ Azure AI Search has the following dimensions associated with the metrics that ca
69
40
|**SkillName**| Name of a skill within a skillset. |
The following table lists common operations related to Azure AI Search that may be recorded in the activity log. For a complete listing of all Microsoft.Search operations, see [Microsoft.Search resource provider operations](/azure/role-based-access-control/resource-provider-operations#microsoftsearch).
@@ -119,13 +86,9 @@ Common entries include references to API keys - generic informational notificati
119
86
120
87
Alternatively, you might gain some insight through change history. In the Azure portal, select the activity to open the detail page and then select "Change history" for information about the underlying operation.
121
88
122
-
<!-- Refer to https://learn.microsoft.com/azure/role-based-access-control/resource-provider-operations and link to the possible operations for your service, using the format - [<Namespace> resource provider operations](/azure/role-based-access-control/resource-provider-operations#<namespace>).
123
-
If there are other operations not in the link, list them here in table form. -->
124
-
125
-
<!-- ## Other schemas. Optional section. Please keep heading in this order. If your service uses other schemas, add the following include and information. -->
<!-- List other schemas and their usage here. These can be resource logs, alerts, event hub formats, etc. depending on what you think is important. You can put JSON messages, API responses not listed in the REST API docs, and other similar types of info here. -->
91
+
129
92
If you're building queries or custom reports, the data structures that contain Azure AI Search resource logs conform to the following schemas.
130
93
131
94
For resource logs sent to blob storage, each blob has one root object called **records** containing an array of log objects. Each blob contains records for all the operations that took place during the same hour.
0 commit comments