Skip to content

Commit 0350cda

Browse files
gmndrggmndrg
authored
Merge branch 'MicrosoftDocs:main' into main
2 parents 462d831 + 8b3dd6e commit 0350cda

31 files changed

+323
-151
lines changed

‎articles/active-directory/cloud-sync/tutorial-basic-ad-azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This tutorial walks you through creating a basic Active Directory environment.
1919

2020
![Diagram that shows a basic Azure A D environment.](media/tutorial-single-forest/diagram-2.png)
2121

22-
You can use the environment you create in the tutorial to test various aspects of hybrid identity scenarios and will be a prerequisite for some of the tutorials. If you already have an existing Active Directory environment you can use that as a substitute. This information is provided for individuals who my be starting from nothing.
22+
You can use the environment you create in the tutorial to test various aspects of hybrid identity scenarios and will be a prerequisite for some of the tutorials. If you already have an existing Active Directory environment you can use that as a substitute. This information is provided for individuals who may be starting from nothing.
2323

2424
This tutorial consists of
2525
## Prerequisites

‎articles/api-management/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -431,6 +431,8 @@
431431
href: virtual-network-reference.md
432432
- name: Self-hosted gateway configuration
433433
href: self-hosted-gateway-settings-reference.md
434+
- name: Diagnostic logs settings
435+
href: diagnostic-logs-reference.md
434436
- name: Resources
435437
items:
436438
- name: FAQ

‎articles/api-management/api-management-howto-app-insights.md

Lines changed: 10 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ To use Application Insights, [create an instance of the Application Insights ser
6161
1. Check the **Enable** box.
6262
1. Select your attached logger in the **Destination** dropdown.
6363
1. Input **100** as **Sampling (%)** and select the **Always log errors** checkbox.
64-
1. Leave the rest of the settings as is.
64+
1. Leave the rest of the settings as is. For details about the settings, see [Diagnostic logs settings reference](diagnostic-logs-reference.md).
6565

6666
> [!WARNING]
6767
> Overriding the default **Number of payload bytes to log** value **0** may significantly decrease the performance of your APIs.
@@ -73,30 +73,15 @@ To use Application Insights, [create an instance of the Application Insights ser
7373
> Requests are successful once API Management sends the entire response to the client.
7474
7575

76-
| Setting name | Value type | Description |
77-
|-------------------------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
78-
| Enable | boolean | Specifies whether logging of this API is enabled. |
79-
| Destination | Azure Application Insights logger | Specifies Azure Application Insights logger to be used. |
80-
| Sampling (%) | decimal | Values from 0 to 100 (percent). <br/> Specifies the percentage of requests that will be logged to Application Insights. 0% sampling means zero requests logged, while 100% sampling means all requests logged. <br/> Use this setting to reduce effect on performance when logging requests to Application Insights. See [Performance implications and log sampling](#performance-implications-and-log-sampling). |
81-
| Always log errors | boolean | If this setting is selected, all failures will be logged to Application Insights, regardless of the **Sampling** setting.
82-
| Log client IP address | | If this setting is selected, the client IP address for API requests will be logged to Application Insights. |
83-
| Verbosity | | Specifies the verbosity level. Only custom traces with higher severity level will be logged. Default: Information. |
84-
| Correlation protocol | | Select protocol used to correlate telemetry sent by multiple components. Default: Legacy <br/>For information, see [Telemetry correlation in Application Insights](../azure-monitor/app/correlation.md). |
85-
| Basic Options: Headers to log | list | Specifies the headers that will be logged to Application Insights for requests and responses. Default: no headers are logged. |
86-
| Basic Options: Number of payload bytes to log | integer | Specifies how many first bytes of the body are logged to Application Insights for requests and responses. Default: 0. |
87-
| Advanced Options: Frontend Request | | Specifies whether and how *frontend requests* will be logged to Application Insights. *Frontend request* is a request incoming to the Azure API Management service. |
88-
| Advanced Options: Frontend Response | | Specifies whether and how *frontend responses* will be logged to Application Insights. *Frontend response* is a response outgoing from the Azure API Management service. |
89-
| Advanced Options: Backend Request | | Specifies whether and how *backend requests* will be logged to Application Insights. *Backend request* is a request outgoing from the Azure API Management service. |
90-
| Advanced Options: Backend Response | | Specifies whether and how *backend responses* will be logged to Application Insights. *Backend response* is a response incoming to the Azure API Management service. |
76+
## Loggers for a single API or all APIs
9177

92-
> [!NOTE]
93-
> You can specify loggers on different levels:
94-
> + Single API logger.
95-
> + A logger for all APIs.
96-
>
97-
> Specifying *both*:
98-
> - By default, the single API logger (more granular level) will override the one for all APIs.
99-
> - If the loggers configured at the two levels are different, and you need both loggers to receive telemetry (multiplexing), please contact Microsoft Support.
78+
You can specify loggers on different levels:
79+
+ Single API logger
80+
+ A logger for all APIs
81+
82+
Specifying *both*:
83+
- By default, the single API logger (more granular level) will override the one for all APIs.
84+
- If the loggers configured at the two levels are different, and you need both loggers to receive telemetry (multiplexing), please contact Microsoft Support.
10085

10186
## What data is added to Application Insights
10287

@@ -146,4 +131,4 @@ To improve performance issues, skip:
146131

147132
+ Learn more about [Azure Application Insights](/azure/application-insights/).
148133
+ Consider [logging with Azure Event Hubs](api-management-howto-log-event-hubs.md).
149-
+ - Learn about visualizing data from Application Insights using [Azure Managed Grafana](visualize-using-managed-grafana-dashboard.md)
134+
+ Learn about visualizing data from Application Insights using [Azure Managed Grafana](visualize-using-managed-grafana-dashboard.md)

0 commit comments

Comments
 (0)