Monitor An Azure AI Search Solution
Monitor an Azure AI Search Solution
Azure Monitor may provide you with information on the performance and usage of your search service.
Additionally, you can get notifications to let you know about problems before they happen.
Monitor Azure AI Search in Azure Monitor
You may view your current search latency, queries per second, and the percentage of throttledqueries as soon as you start up your Azure AI Search service.
The Monitoring tab of the Overview page displays this data.
You can also check what resources your search solution is using on the Usage
tab.
You can monitor with additional setup, but this basic information is an excellent place to start.You will be aware that Azure Monitor can be utilized for all of your Azure resources if you are accustomed to maintaining other Azure platform resources.
Once you have started
using Log Analytics, you get access to performance and diagnostic data in these
log tables:
- AzureActivity -
Shows you tasks that have been executed like scaling the search service
- AzureDiagnostics -
All the query and indexing operations
- AzureMetrics
- Data used for metrics that measure the health and performance of your search
service
Use Metrics To See Diagnostic
Data Visually
Making charts is an effective approach to see the performance of your search service.
Choose Metrics from your search service's Monitoring section.
Now select to add any of
these captured metrics:
- DocumentsProcessedCount
- SearchLatency
- SearchQueriesPerSecond
- SkillExecutionCount
- ThrottledSearchQueriesPercentage
For example, you could
plot search latency against the percentage of throttled queries to see if the
responses to queries are affected by throttling.
Write Kusto Queries Against
Your Search Solutions Logs
Any Kusto query can be written against recorded log data using Log Analytics.
Choosing Logs from the Monitor section is the simplest approach to execute these queries.
With the query window automatically scoped to your Azure AI Search solution, Logs launches Log Analytics.
Create Alerts To Be Notified
About Common Search Solution Issues
Alerts can let you
proactively manage your search service. Here are some commonly used alerts you
should consider creating.
- Search Latency
using the metric signal, you can specify what latency triggers the alert in
seconds
- Throttled search
percentage using the metric signal, you can specify the
percentage
- Delete Search Service
using the activity log signal, be notified if your search service is deleted
- Stop Search Service
using the activity log signal, be notified if your search service is stopped
which happens if your search service is scaled up or down or needs to be
restarted
Conclusion
We have successfully
learnt about monitoring an Azure AI Search solution.
Comments
Post a Comment