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/search/monitor-azure-cognitive-search.md
+3-27Lines changed: 3 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,42 +3,18 @@ title: Monitor Azure AI Search
3
3
description: Start here to learn how to monitor Azure AI Search.
4
4
ms.date: 01/27/2025
5
5
ms.custom: horz-monitor
6
-
ms.topic: how-to
6
+
ms.topic: conceptual
7
7
author: HeidiSteen
8
8
ms.author: heidist
9
9
ms.service: azure-ai-search
10
10
---
11
11
12
12
# Monitor Azure AI Search
13
13
14
-
This article explains how to configure logging and where to find information about search service operations.
15
-
16
-
## Enable diagnostic logging
17
-
18
-
Resource logging is available through Azure Monitor. Although some search service activity is reported automatically with no upfront configuration, resource logs about operations and data access require that you create a diagnostic setting and specify a storage option.
19
-
20
-
If you create more than one diagnostic setting, you must have different destinations for each one.
21
-
22
-
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your search service.
23
-
24
-
1. Under **Monitoring** > **Diagnostic settings**, select **Add diagnostic setting**.
25
-
26
-
1. Provide a name that identifies the service and level of logging, such as "my-search-service-all-logs" or "my-search-service-audit-logs".
27
-
28
-
1. Under **Logs**, choose a category:
29
-
30
-
-**audit** to capture information about user and group identity access to content and operations
31
-
-**Operation Logs** to capture information about operations on a search service.
32
-
-**allLogs** to collect everything.
33
-
34
-
Verbose logging can be expensive to store and complex to manage and store. You might want to start with **allLogs** and then switch to more scoped logging if it meets your information requirements.
35
-
36
-
1. For a destination, we recommend **Send to Log Analytics workspace** so that you can run Kusto queries against the data.
> If you're using [key-based authentication](search-security-api-keys.md), Azure AI Search can't monitor individual user access to content on the search service. If you require this level of monitoring, you need to implement it in your client application.
17
+
> Azure AI Search doesn't log the identity of the person or app accessing content or operations on the search service. If you require this level of monitoring, you need to implement it in your client application.
0 commit comments