fix links and correct one more article

Author: rboucher

articles/azure-monitor/platform/diagnostic-logs-schema.md

@@ -44,12 +44,12 @@ The schema for resource diagnostic logs varies depending on the resource and log
 | --- | --- |
 | Azure Active Directory | [Overview](../../active-directory/reports-monitoring/concept-activity-logs-azure-monitor.md), [Audit log schema](../../active-directory/reports-monitoring/reference-azure-monitor-audit-log-schema.md) and [Sign-ins schema](../../active-directory/reports-monitoring/reference-azure-monitor-sign-ins-log-schema.md) |
 | Analysis Services | https://azure.microsoft.com/blog/azure-analysis-services-integration-with-azure-diagnostic-logs/ |
-| API Management | [API Management Resource Logs](../../api-management/api-management-howto-use-azure-monitor.md#diagnostic-logs) |
+| API Management | [API Management Resource Logs](../../api-management/api-management-howto-use-azure-monitor.md#resource-logs) |
 | Application Gateways |[Logging for Application Gateway](../../application-gateway/application-gateway-diagnostics.md) |
 | Azure Automation |[Log analytics for Azure Automation](../../automation/automation-manage-send-joblogs-log-analytics.md) |
 | Azure Batch |[Azure Batch logging](../../batch/batch-diagnostics.md) |
-| Azure Database for MySQL | [Azure Database for MySQL diagnostic logs](../../mysql/concepts-server-logs.md#diagnostic-logs) |
-| Azure Database for PostgreSQL | [Azure Database for PostgreSQL logs](../../postgresql/concepts-server-logs.md#diagnostic-logs) |
+| Azure Database for MySQL | [Azure Database for MySQL diagnostic logs](../../mysql/concepts-server-logs.md#resource-logs) |
+| Azure Database for PostgreSQL | [Azure Database for PostgreSQL logs](../../postgresql/concepts-server-logs.md#resource-logs) |
 | Azure Data Explorer | [Azure Data Explorer logs](/azure/data-explorer/using-diagnostic-logs) |
 | Cognitive Services | [Logging for Azure Cognitive Services](../../cognitive-services/diagnostic-logging.md) |
 | Container Registry | [Logging for Azure Container Registry](../../container-registry/container-registry-diagnostics-audit-logs.md) |

articles/azure-signalr/signalr-tutorial-diagnostic-logs.md

@@ -1,38 +1,38 @@
 ---
-title: Diagnostic Logs for Azure SignalR Service
-description: Learn how to set up diagnostic logs for Azure SignalR Service and how to utilize it to self-troubleshoot.
+title: Resource Logs for Azure SignalR Service
+description: Learn how to set up resource logs for Azure SignalR Service and how to utilize it to self-troubleshoot.
 author: wanlwanl
 ms.service: signalr
 ms.topic: conceptual
 ms.date: 12/17/2019
 ms.author: wanl
 ---
 
-# Diagnostic Logs for Azure SignalR Service
+# Resource logs for Azure SignalR Service
 
-This tutorial covers what are diagnostic logs for Azure SignalR Service and how to set up diagnostic logs and how to troubleshoot with diagnostic logs.
+This tutorial discusses what resource logs for Azure SignalR Service are, how to set them up, and how to troubleshoot with them. 
 
 ## Prerequisites
-To enable diagnostic logs, you'll need somewhere to store your log data. This tutorial uses Azure Storage and Log Analytics.
+To enable resource logs, you'll need somewhere to store your log data. This tutorial uses Azure Storage and Log Analytics.
 
-* [Azure storage](../azure-monitor/platform/resource-logs-collect-storage.md) - Retains diagnostic logs for policy audit, static analysis, or backup.
+* [Azure storage](../azure-monitor/platform/resource-logs-collect-storage.md) - Retains resource logs for policy audit, static analysis, or backup.
 * [Log Analytics](../azure-monitor/platform/resource-logs-collect-workspace.md) - A flexible log search and analytics tool that allows for analysis of raw logs generated by an Azure resource.
 
-## Set up diagnostic logs for an Azure SignalR Service
+## Set up resource logs for an Azure SignalR Service
 
-You can view diagnostic logs for Azure SignalR Service. These logs provide richer view of connectivity to your Azure SignalR Service instance. The diagnostic logs provide detailed information of every connection. For example, basic information (user ID, connection ID and transport type and so on) and event information (connect, disconnect and abort event and so on) of the connection. Diagnostic logs can be used for issue identification, connection tracking and analysis.
+You can view resource logs for Azure SignalR Service. These logs provide richer view of connectivity to your Azure SignalR Service instance. The resource logs provide detailed information of every connection. For example, basic information (user ID, connection ID and transport type and so on) and event information (connect, disconnect and abort event and so on) of the connection. resource logs can be used for issue identification, connection tracking and analysis.
 
-### Enable diagnostic logs
+### Enable resource logs
 
-Diagnostic logs are disabled by default. To enable diagnostic logs, follow these steps:
+Resource logs are disabled by default. To enable resource logs, follow these steps:
 
 1. In the [Azure portal](https://portal.azure.com), under **Monitoring**, click **Diagnostic settings**.
 
     ![Pane navigation to diagnostic settings](./media/signalr-tutorial-diagnostic-logs/diagnostic-settings-menu-item.png)
 
 1. Then click **Add diagnostic setting**.
 
-    ![Add diagnostic logs](./media/signalr-tutorial-diagnostic-logs/add-diagnostic-setting.png)
+    ![Add resource logs](./media/signalr-tutorial-diagnostic-logs/add-diagnostic-setting.png)
 
 1. Set the archive target that you want. Currently, we support **Archive to a storage account** and **Send to Log Analytics**.
 
@@ -45,17 +45,17 @@ Diagnostic logs are disabled by default. To enable diagnostic logs, follow these
 
 New settings take effect in about 10 minutes. After that, logs appear in the configured archival target, in the **Diagnostics logs** pane.
 
-For more information about configuring diagnostics, see the [overview of Azure diagnostic logs](../azure-monitor/platform/platform-logs-overview.md).
+For more information about configuring diagnostics, see the [overview of Azure resource logs](../azure-monitor/platform/platform-logs-overview.md).
 
-### Diagnostic logs categories
+### Resource logs categories
 
-Azure SignalR Service captures diagnostic logs in one category:
+Azure SignalR Service captures resource logs in one category:
 
 * **All Logs**: Track connections that connect to Azure SignalR Service. The logs provide information about the connect/disconnect, authentication and throttling. For more information, see the next section.
 
 ### Archive to a storage account
 
-Logs are stored in the storage account that configured in **Diagnostics logs** pane. A container named `insights-logs-alllogs` is created automatically to store diagnostic logs. Inside the container, logs are stored in the file `resourceId=/SUBSCRIPTIONS/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/RESOURCEGROUPS/XXXX/PROVIDERS/MICROSOFT.SIGNALRSERVICE/SIGNALR/XXX/y=YYYY/m=MM/d=DD/h=HH/m=00/PT1H.json`. Basically, the path is combined by `resource ID` and `Date Time`. The log files are split by `hour`. Therefore, the minutes always be `m=00`.
+Logs are stored in the storage account that configured in **Diagnostics logs** pane. A container named `insights-logs-alllogs` is created automatically to store resource logs. Inside the container, logs are stored in the file `resourceId=/SUBSCRIPTIONS/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/RESOURCEGROUPS/XXXX/PROVIDERS/MICROSOFT.SIGNALRSERVICE/SIGNALR/XXX/y=YYYY/m=MM/d=DD/h=HH/m=00/PT1H.json`. Basically, the path is combined by `resource ID` and `Date Time`. The log files are split by `hour`. Therefore, the minutes always be `m=00`.
 
 All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
 
@@ -111,13 +111,13 @@ The following code is an example of an archive log JSON string:
 
 ### Archive logs schema for Log Analytics
 
-To view diagnostic logs, follow these steps:
+To view resource logs, follow these steps:
 
 1. Click `Logs` in your target Log Analytics.
 
     ![Log Analytics menu item](./media/signalr-tutorial-diagnostic-logs/log-analytics-menu-item.png)
 
-2. Enter `SignalRServiceDiagnosticLogs` and select time range to query diagnostic logs. For advanced query, see [Get started with Log Analytics in Azure Monitor](../azure-monitor/log-query/get-started-portal.md)
+2. Enter `SignalRServiceDiagnosticLogs` and select time range to query resource logs. For advanced query, see [Get started with Log Analytics in Azure Monitor](../azure-monitor/log-query/get-started-portal.md)
 
     ![Query log in Log Analytics](./media/signalr-tutorial-diagnostic-logs/query-log-in-log-analytics.png)
 
@@ -137,11 +137,11 @@ ConnectionId | Identity of the connection
 ConnectionType | Type of the connection. Allowed values are: `Server` \| `Client`. `Server`: connection from server side; `Client`: connection from client side
 TransportType | Transport type of the connection. Allowed values are: `Websockets` \| `ServerSentEvents` \| `LongPolling`
 
-### Troubleshooting with diagnostic logs
+### Troubleshooting with resource logs
 
-To troubleshoot for Azure SignalR Service, you can enable server/client side logs to capture failures. At present, Azure SignalR Service exposes diagnostic logs, you can also enable logs for service side.
+To troubleshoot for Azure SignalR Service, you can enable server/client side logs to capture failures. At present, Azure SignalR Service exposes resource logs, you can also enable logs for service side.
 
-When encountering connection unexpected growing or dropping situation, you can take advantage of diagnostic logs to troubleshoot.
+When encountering connection unexpected growing or dropping situation, you can take advantage of resource logs to troubleshoot.
 
 Typical issues are often about connections' unexpected quantity changes, connections reach connection limits and authorization failure. See the next sections about how to troubleshoot.
 
@@ -151,7 +151,7 @@ Typical issues are often about connections' unexpected quantity changes, connect
 
 If you encounter unexpected connections drop, firstly enable logs in service, server and client sides.
 
-If a connection disconnects, the diagnostic logs will record this disconnecting event, you will see `ConnectionAborted` or `ConnectionEnded` in `operationName`.
+If a connection disconnects, the resource logs will record this disconnecting event, you will see `ConnectionAborted` or `ConnectionEnded` in `operationName`.
 
 The difference between `ConnectionAborted` and `ConnectionEnded` is that `ConnectionEnded` is an expected disconnecting which is triggered by client or server side. While the `ConnectionAborted` is usually an unexpected connection dropping event, and aborting reason will be provided in `message`.
 
@@ -168,20 +168,20 @@ Server connection dropped | Server connection drops with unknown error, consider
 
 ##### Unexpected connection growing
 
-To troubleshoot about unexpected connection growing, the first thing you need to do is to filter out the extra connections. You can add unique test user ID to your test client connection. Then verify it in with diagnostic logs, if you see more than one client connections have the same test user ID or IP, then it is likely the client side create and establish more connections than expectation. Check your client side.
+To troubleshoot about unexpected connection growing, the first thing you need to do is to filter out the extra connections. You can add unique test user ID to your test client connection. Then verify it in with resource logs, if you see more than one client connections have the same test user ID or IP, then it is likely the client side create and establish more connections than expectation. Check your client side.
 
 #### Authorization failure
 
-If you get 401 Unauthorized returned for client requests, check your diagnostic logs. If you encounter `Failed to validate audience. Expected Audiences: <valid audience>. Actual Audiences: <actual audience>`, it means all audiences in your access token are invalid. Try to use the valid audiences suggested in the log.
+If you get 401 Unauthorized returned for client requests, check your resource logs. If you encounter `Failed to validate audience. Expected Audiences: <valid audience>. Actual Audiences: <actual audience>`, it means all audiences in your access token are invalid. Try to use the valid audiences suggested in the log.
 
 
 #### Throttling
 
-If you find that you cannot establish SignalR client connections to Azure SignalR Service, check your diagnostic logs. If you encounter `Connection count reaches limit` in diagnostic log, you establish too many connections to SignalR Service, which reach the connection count limit. Consider scaling up your SignalR Service. If you encounter `Message count reaches limit` in diagnostic log, it means you use free tier, and you use up the quota of messages. If you want to send more messages, consider changing your SignalR Service to standard tier to send additional messages. For more information, see [Azure SignalR Service Pricing](https://azure.microsoft.com/pricing/details/signalr-service/).
+If you find that you cannot establish SignalR client connections to Azure SignalR Service, check your resource logs. If you encounter `Connection count reaches limit` in resource log, you establish too many connections to SignalR Service, which reach the connection count limit. Consider scaling up your SignalR Service. If you encounter `Message count reaches limit` in resource log, it means you use free tier, and you use up the quota of messages. If you want to send more messages, consider changing your SignalR Service to standard tier to send additional messages. For more information, see [Azure SignalR Service Pricing](https://azure.microsoft.com/pricing/details/signalr-service/).
 
 ### Get help
 
-We recommend you troubleshoot by yourself first. Most issues are caused by app server or network issues. Follow [troubleshooting guide with diagnostic log](#troubleshooting-with-diagnostic-logs) and [basic trouble shooting guide](https://github.com/Azure/azure-signalr/blob/dev/docs/tsg.md) to find the root cause.
+We recommend you troubleshoot by yourself first. Most issues are caused by app server or network issues. Follow [troubleshooting guide with resource log](#troubleshooting-with-diagnostic-logs) and [basic trouble shooting guide](https://github.com/Azure/azure-signalr/blob/dev/docs/tsg.md) to find the root cause.
 If the issue still can't be resolved, then consider open an issue in GitHub or create ticket in Azure Portal.
 Provide:
 1. Time range about 30 minutes when the issue occurs

articles/bastion/diagnostic-logs.md

@@ -1,5 +1,5 @@
 ---
-title: 'Enable and work with Azure Bastion diagnostic logs'
+title: 'Enable and work with Azure Bastion resource logs'
 description: In this article, learn how to enable and work with Azure Bastion diagnostic logs.
 services: bastion
 author: charwen
@@ -11,11 +11,11 @@ ms.author: charwen
 
 ---
 
-# Enable and work with Bastion diagnostic logs
+# Enable and work with Bastion resource logs
 
 As users connect to workloads using Azure Bastion, Bastion can log diagnostics of the remote sessions. You can then use the diagnostics to view which users connected to which workloads, at what time, from where, and other such relevant logging information. In order to use the diagnostics, you must enable diagnostics logs on Azure Bastion. This article helps you enable diagnostics logs, and then view the logs.
 
-## <a name="enable"></a>Enable the diagnostics log
+## <a name="enable"></a>Enable the resource log
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your Azure Bastion resource and select **Diagnostics settings** from the Azure Bastion page.
 
@@ -40,7 +40,7 @@ To access your diagnostics logs, you can directly use the storage account that y
 2. As you navigate to inside the container, you see various folders in your blog. These folders indicate the resource hierarchy for your Azure Bastion resource.
 
    ![add diagnostic setting](./media/diagnostic-logs/2-resource-h.png)
-3. Navigate to the full hierarchy of your Azure Bastion resource whose diagnostics logs you wish to access/view. The 'y=', 'm=', 'd=', 'h=' and 'm=' indicate the year, month, day, hour, and minute respectively for the diagnostic logs.
+3. Navigate to the full hierarchy of your Azure Bastion resource whose diagnostics logs you wish to access/view. The 'y=', 'm=', 'd=', 'h=' and 'm=' indicate the year, month, day, hour, and minute respectively for the resource logs.
 
    ![select storage location](./media/diagnostic-logs/3-resource-location.png)
 4. Locate the json file created by Azure Bastion that contains the diagnostics log data for the time-period navigated to.