Skip to content

Commit bed5c56

Browse files
committed
Freshness pass on monitoring articles
1 parent cbc30b3 commit bed5c56

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

articles/search/samples-rest.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: HeidiSteen
88
ms.author: heidist
99
ms.service: cognitive-search
1010
ms.topic: conceptual
11-
ms.date: 01/27/2021
11+
ms.date: 09/15/2022
1212
---
1313

1414
# REST code samples for Azure Cognitive Search
@@ -19,8 +19,8 @@ REST is the definitive programming interface for Azure Cognitive Search, and all
1919

2020
REST samples are usually developed and tested on Postman, but you can use any client that supports HTTP calls:
2121

22-
+ Start with [Quickstart: Create an Azure Cognitive Search index using REST APIs](search-get-started-rest.md) for help in formulating HTTP calls.
23-
+ Try [Visual Studio Code extension for Azure Cognitive Search](search-get-started-vs-code.md), currently in preview, if you work in Visual Studio Code.
22+
+ [Use Postman](search-get-started-rest.md). This quickstart explains how to formulate the HTTP request from end-to-end.
23+
+ [Use the Visual Studio Code extension for Azure Cognitive Search](search-get-started-vs-code.md), currently in preview. This quickstart uses Azure integration and builds the requests internally, which means you can complete tasks more quickly.
2424

2525
## Doc samples
2626

@@ -36,7 +36,7 @@ Code samples from the Cognitive Search team demonstrate features and workflows.
3636
| [projections](https://github.com/Azure-Samples/azure-search-postman-samples/tree/master/projections) | Source code for [Define projections in a knowledge store](knowledge-store-projections-examples.md). This article explains how to specify the physical data structures in a knowledge store.|
3737
| [index-encrypted-blobs](https://github.com/Azure-Samples/azure-search-postman-samples/commit/f5ebb141f1ff98f571ab84ac59dcd6fd06a46718) | Source code for [How to index encrypted blobs using blob indexers and skillsets](search-howto-index-encrypted-blobs.md). This article shows how to index documents in Azure Blob Storage that have been previously encrypted using Azure Key Vault. |
3838

39-
> [!Tip]
39+
> [!TIP]
4040
> Try the [Samples browser](/samples/browse/?expanded=azure&languages=http&products=azure-cognitive-search) to search for Microsoft code samples in GitHub, filtered by product, service, and language.
4141
4242
## Other samples

articles/search/search-howto-monitor-indexers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: HeidiSteen
88
ms.author: heidist
99
ms.service: cognitive-search
1010
ms.topic: conceptual
11-
ms.date: 01/28/2021
11+
ms.date: 09/15/2022
1212
---
1313

1414
# Monitor indexer status and results in Azure Cognitive Search
@@ -17,13 +17,13 @@ You can monitor indexer processing in the Azure portal, or programmatically thro
1717

1818
## Monitor using Azure portal
1919

20-
You can see the current status of all of your indexers in your search service Overview page. Portal pages refresh every few minutes, so you won't see evidence of a new indexer run right away.
20+
You can see the current status of all of your indexers in your search service Overview page. Portal pages refresh every few minutes, so you won't see evidence of a new indexer run right away. Select **Refresh** at the top of the page to immediately retrieve the most recent view.
2121

2222
![Indexers list](media/search-monitor-indexers/indexers-list.png "Indexers list")
2323

2424
| Status | Description |
2525
|--------|-------------|
26-
| **In Progress** | Indicates active execution. The portal will report on partial information. As indexing progresses, you can watch the **Docs Succeeded** value grow in response. Indexers that process large volumes of data can take a long time to run. For example, indexers that handle millions of source documents can run for 24 hours, and then restart almost immediately. The status for high-volume indexers might always say **In Progress** in the portal. Even when an indexer is running, details are available about ongoing progress and previous runs. |
26+
| **In Progress** | Indicates active execution. The portal will report on partial information. As indexing progresses, you can watch the **Docs Succeeded** value grow in response. Indexers that process large volumes of data can take a long time to run. For example, indexers that handle millions of source documents can run for 24 hours, and then restart almost immediately to pick up where it left off. As such, the status for high-volume indexers might always say **In Progress** in the portal. Even when an indexer is running, details are available about ongoing progress and previous runs. |
2727
| **Success** | Indicates the run was successful. An indexer run can be successful even if individual documents have errors, if the number of errors is less than the indexer's **Max failed items** setting. |
2828
| **Failed** | The number of errors exceeded **Max failed items** and indexing has stopped. |
2929
| **Reset** | The indexer's internal change tracking state was reset. The indexer will run in full, refreshing all documents, and not just those with newer timestamps. |

articles/search/search-indexer-field-mappings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 09/14/2022
1616

1717
![Indexer Stages](./media/search-indexer-field-mappings/indexer-stages-field-mappings.png "indexer stages")
1818

19-
When an [Azure Cognitive Search indexer](search-indexer-overview.md) loads a search index, it determines the data path through source-to-destination field mappings. Implicit field mappings are internal and occur when field names and data types are compatible between the source and destination.
19+
When an [Azure Cognitive Search indexer](search-indexer-overview.md) loads a search index, it determines the data path through source-to-destination field mappings. Implicit field mappings are internal and occur when field names and data types are compatible between the source and destination.
2020

2121
If inputs and outputs don't match, you can define explicit *field mappings* to set up the data path, as described in this article. Field mappings can also be used to introduce light-weight data conversion, such as encoding or decoding, through [mapping functions](#mappingFunctions). If more processing is required, consider [Azure Data Factory](../data-factory/index.yml) to bridge the gap.
2222

articles/search/search-monitor-logs-powerbi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88

99
ms.service: cognitive-search
1010
ms.topic: conceptual
11-
ms.date: 04/07/2021
11+
ms.date: 09/15/2022
1212
---
1313

1414
# Visualize Azure Cognitive Search Logs and Metrics with Power BI

0 commit comments

Comments
 (0)