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
SearchQueriesPerSecond shows the average of the search queries per second (QPS) for the search service. It's common for queries to execute in milliseconds, so only queries that measure as seconds appear in a metric like QPS. The minimum is the lowest value for search queries per second that was registered during that minute. Maximum is the highest value. Average is the aggregate across the entire minute.
54
54
55
55
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".
61
61
@@ -70,15 +70,15 @@ Azure AI Search has the following dimensions associated with the metrics that ca
|[AzureDiagnostics](/azure/azure-monitor/reference/tables/azurediagnostics)| Logged query and indexing operations. Queries against the AzureDiagnostics table in Log Analytics can include the common properties, the [search-specific properties](#resource-log-search-props), and the [search-specific operations](#resource-log-search-ops) listed in the schema reference section. |
89
89
|[AzureMetrics](/azure/azure-monitor/reference/tables/azuremetrics)| Metric data emitted by Azure AI Search that measures health and performance. |
90
90
91
+
### Resource log tables
92
+
93
+
The following table lists the properties of resource logs in Azure AI Search. The resource logs are collected into Azure Monitor Logs or Azure Storage. In Azure Monitor, logs are collected in the AzureDiagnostics table under the resource provider name of `Microsoft.Search`.
94
+
95
+
| Azure Storage field or property | Azure Monitor Logs property | Description |
96
+
|-|-|-|
97
+
| time | TIMESTAMP | The date and time (UTC) when the operation occurred. |
98
+
| resourceId | Concat("/", "/subscriptions", SubscriptionId, "resourceGroups", ResourceGroupName, "providers/Microsoft.Search/searchServices", ServiceName) | The Azure AI Search resource for which logs are enabled. |
99
+
| category | "OperationLogs" | Log categories include `Audit`, `Operational`, `Execution`, and `Request`. |
100
+
| operationName | Name | Name of the operation. The operation name can be `Indexes.ListIndexStatsSummaries`, `Indexes.Get`, `Indexes.Stats`, `Indexers.List`, `Query.Search`, `Query.Suggest`, `Query.Lookup`, `Query.Autocomplete`, `CORS.Preflight`, `Indexes.Update`, `Indexes.Prototype`, `ServiceStats`, `DataSources.List`, `Indexers.Warmup`. |
101
+
| durationMS | DurationMilliseconds | The duration of the operation, in milliseconds. |
102
+
| operationVersion | ApiVersion | The API version used on the request. |
103
+
| resultType | (Failed) ? "Failed" : "Success" | The type of response. |
104
+
| resultSignature | Status | The HTTP response status of the operation. |
105
+
| properties | Properties | Any extended properties related to this category of events. |
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).
95
111
@@ -108,14 +124,13 @@ If there are other operations not in the link, list them here in table form. -->
108
124
109
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. -->
113
129
If you're building queries or custom reports, the data structures that contain Azure AI Search resource logs conform to the following schemas.
114
130
115
131
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.
116
132
117
133
<aname="resource-log-schema"></a>
118
-
119
134
### Resource log schema
120
135
121
136
All resource logs available through Azure Monitor share a [common top-level schema](/azure/azure-monitor/essentials/resource-logs-schema#top-level-common-schema). Azure AI Search supplements with [more properties](#resource-log-search-props) and [operations](#resource-log-search-ops) that are unique to a search service.
0 commit comments