-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update azure-bing-search-monitoring-integration.mdx
- Loading branch information
Showing
1 changed file
with
123 additions
and
0 deletions.
There are no files selected for viewing
123 changes: 123 additions & 0 deletions
123
...tegrations/azure-integrations-list/azure-bing-search-monitoring-integration.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,124 @@ | ||
| --- | ||
| title: Azure Bing Search service through Azure Monitor integration | ||
| metaDescription: "New Relic's Microsoft Azure Bing Search integration: what data it reports and how to enable it." | ||
| --- | ||
|
|
||
| [New Relic's integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your [Microsoft Azure Bing Search](https://learn.microsoft.com/en-us/bing/search-apis/bing-web-search/) metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported. | ||
|
|
||
| ## Features | ||
|
|
||
| New Relic gathers metrics data from Azure Monitor for the Azure Bing Search service. Azure Bing Search services provide developers with an easy-to-use platform for integrating search and AI capabilities into their applications. | ||
|
|
||
| Using New Relic, you can: | ||
|
|
||
| * View Azure Bing Search services data in pre-built dashboards. | ||
| * Run [custom queries and visualize the data](/docs/infrastructure/integrations-getting-started/getting-started/use-integration-data-new-relic-insights). | ||
| * Create alert conditions to notify you of changes in data. | ||
|
|
||
| ## Activate integration [#activate] | ||
|
|
||
| Follow standard [Azure Monitor integration procedure](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor) to activate your Azure service in New Relic infrastructure monitoring. | ||
|
|
||
| ## Configuration and polling [#polling] | ||
|
|
||
| You can change the polling frequency and filter data using [configuration options](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#settings). | ||
|
|
||
| New Relic queries your Azure Bing Search services through Azure Monitor integration according to a default [polling](/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-monitor/#settings) interval. | ||
|
|
||
| ## Find and use data [#find-and-use] | ||
|
|
||
| To [explore your integration data](/docs/infrastructure/integrations/find-use-infrastructure-integration-data), go to **[one.newrelic.com/infra](https://one.newrelic.com/infra) > Azure > (select an integration)**. | ||
|
|
||
| ## Metric data [#metrics] | ||
|
|
||
| This integration collects the following [metric data](/docs/infrastructure/integrations-getting-started/getting-started/understand-integration-data-data-types#metric). | ||
|
|
||
| ### Azure Bing Search metrics [#Azure-bing-search] | ||
|
|
||
| <table> | ||
| <thead> | ||
| <tr> | ||
| <th style={{ width: "300px" }}> | ||
| Metric | ||
| </th> | ||
| <th> | ||
| Description | ||
| </th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td> | ||
| `BlockedCalls` | ||
| </td> | ||
| <td> | ||
| Number of calls that exceeded the rate or quota limit. | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `ClientErrors` | ||
| </td> | ||
|
|
||
| <td> | ||
| Number of calls with any client error (HTTP status code 4xx). | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `DataIn` | ||
| </td> | ||
| <td> | ||
| Incoming request Content-Length in bytes. | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `DataOut` | ||
| </td> | ||
| <td> | ||
| Outgoing response Content-Length in bytes. | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `Latency` | ||
| </td> | ||
| <td> | ||
| Latency in milliseconds. | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `ServerErrors` | ||
| </td> | ||
| <td> | ||
| Number of calls with any server error (HTTP status code 5xx). | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `SuccessfulCalls` | ||
| </td> | ||
| <td> | ||
| Number of successful calls (HTTP status code 2xx). | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `TotalCalls` | ||
| </td> | ||
| <td> | ||
| Total number of calls. | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td> | ||
| `TotalErrors` | ||
| </td> | ||
| <td> | ||
| Number of calls with any error (HTTP status code 4xx or 5xx). | ||
| </td> | ||
| </tr> | ||
| </tbody> | ||
| </table> |