updated based on feedback from Bryan

Author: spelluru

articles/service-bus-relay/diagnostic-logs.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Relay - diagnostics logs | Microsoft Docs
+title: Diagnostics logs for Hybrid Connections
 description: This article provides an overview of all the operational and diagnostics logs that are available for Azure Relay. 
 services: service-bus-messaging
 author: spelluru
@@ -14,21 +14,23 @@ ms.date: 04/27/2020
 ms.author: spelluru
 
 ---
-# Enable diagnostics logs for Azure Relay
-When you start using your Azure Relay namespace, you might want to monitor how and when your namespace is created, deleted, or accessed. This article provides an overview of all the operational and diagnostics logs that are available.
+# Enable diagnostics logs for Azure Relay Hybrid Connections
+When you start using your Azure Relay Hybrid Connections, you might want to monitor how and when your listeners and senders are opened and closed, and how your Hybrid Connections messages are created and sent. This article provides an overview of all the operational and diagnostics logs that are available.
 
 You can view two types of logs for Azure Relay:
 
 - [Activity logs](../azure-monitor/platform/platform-logs-overview.md): These logs have information about operations performed against your namespace in the Azure portal or through Azure Resource Manager template. These logs are always enabled. For example: "Create or update namespace", "Create or update hybrid connection". 
-- [Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md): You can configure diagnostic logs for a richer view of everything that happens with operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK.
+- [Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md): You can configure diagnostic logs for a richer view of everything that happens with operations and actions that are conducted against your namespace by using the API, or through language SDK.
 
 ## View activity logs
 To view activity logs for your Azure Relay namespace, switch to the **Activity log** page in the Azure portal.
 
 ![Azure Relay - activity log](./media/diagnostic-logs/activity-log.png)
 
 ## Enable diagnostic logs
-Only one category: Hybrid Connections
+
+> [!NOTE]
+> Diagnostic logs are available only for hybrid connections, not for Windows Communication Foundation (WCF() relays.
 
 To enable diagnostics logs, do the following steps:
 
@@ -39,7 +41,7 @@ To enable diagnostics logs, do the following steps:
 
 1. Configure the diagnostics settings by doing the following steps:
     1. In the **Name** box, enter a name for the diagnostics settings.  
-    2. Select **HybridConnectionsEvent** for the type of log. It's the only type supported. 
+    2. Select **HybridConnectionsEvent** for the type of log. 
     3. Select one of the following three **destinations** for your diagnostics logs:  
         1. If you select **Archive to a storage account**, configure the storage account where the diagnostics logs will be stored.  
         2. If you select **Stream to an event hub**, configure the event hub that you want to stream the diagnostics logs to.
@@ -59,10 +61,10 @@ Hybrid connections event log JSON strings include the elements listed in the fol
 | ResourceId | Azure Resource Manager resource ID |
 | ActivityId | Internal ID, used to identify the specified operation. May also be known as "TrackingId" |
 | Endpoint | The address of the Relay resource |
-| OperationName | The type of the HybridConnection operation that’s  being logged |
+| OperationName | The type of the Hybrid Connections operation that’s  being logged |
 | EventTimeString | The UTC timestamp of the log record |
 | Message | The detailed message of the event |
-| Category | Category of the event. Currently, it's only `HybridConnectionsEvents`. 
+| Category | Category of the event. Currently, there is only `HybridConnectionsEvents`. 
 
 
 ## Sample hybrid connections event
@@ -72,7 +74,7 @@ Here's a sample hybrid connections event in JSON format.
 {
     "resourceId": "/SUBSCRIPTIONS/0000000000-0000-0000-0000-0000000000000/RESOURCEGROUPS/MyResourceGroup/PROVIDERS/MICROSOFT.RELAY/NAMESPACES/MyRelayNamespace",
     "ActivityId": "7006a0db-27eb-445c-939b-ce86133014cc",
-    "endpoint": "sb://myrelayns.servicebus.windows.net/mhybridconnection/7006a0db-27eb-445c-939b-ce86133014cc_G5",
+    "endpoint": "sb://myrelaynamespace.servicebus.windows.net/myhybridconnection/7006a0db-27eb-445c-939b-ce86133014cc_G5",
     "operationName": "Microsoft.Relay/HybridConnections/NewSenderRegistering",
     "EventTimeString": "2020-04-27T20:27:57.3842810Z",
     "message": "A new on-premises sender is registering.",
@@ -86,25 +88,25 @@ Here's a sample hybrid connections event in JSON format.
 | --------- | ----------- | 
 | AuthorizationFailed | Authorization failed.|
 | InvalidSasToken | Invalid SAS token. | 
-| ListenerAcceptingConnection | The listener is accepting connection. |
-| ListenerAcceptingConnectionTimeout | The listener accepting connection timed out. |
-| ListenerAcceptingHttpRequestFailed | The listener accepting HTTP request failed. |
-| ListenerAcceptingRequestTimeout | The listener accepting request timed out. |  
-| ListenerClosingFromExpiredToken | The listener is closing because of an expired token. | 
-| ListenerRejectedConnection | The listener rejected connection. |
-| ListenerReturningHttpResponse | The listener returning an HTTP response. |  
-| ListenerReturningHttpResponseFailed | The listener returning an HTTP response failed. | 
- ListenerSentHttpResponse | The listener sent an HTTP response. | 
+| ListenerAcceptingConnection | The on-prem listener is accepting connection. |
+| ListenerAcceptingConnectionTimeout | The on-prem listener accepting connection has timed out. |
+| ListenerAcceptingHttpRequestFailed | The listener accepting HTTP request failed due to an exception. |
+| ListenerAcceptingRequestTimeout | The listener accepting request has timed out. |  
+| ListenerClosingFromExpiredToken | The listener is closing because the security token has expired. | 
+| ListenerRejectedConnection | The on-prem listener has rejected the connection. |
+| ListenerReturningHttpResponse | The on-prem listener is returning an HTTP response. |  
+| ListenerReturningHttpResponseFailed | The listener is returning an HTTP response with a failure code. | 
+ ListenerSentHttpResponse | Relay service has received an HTTP response from the on-prem listener. | 
 | ListenerUnregistered | The listener is unregistered. | 
-| ListenerUnresponsive | The listener is unresponsive. | 
+| ListenerUnresponsive | The on-prem listener is unresponsive when returning a response. | 
 | MessageSendingToOnPremListener | Message is being sent to on-premises listener. |
 | MessageSentToOnPremListener | Message is sent to on-premises listener. | 
 | NewListenerRegistered | New listener registered. |
-| NewSenderRegistering | New listener registering. | 
-| ProcessingRequestFailed | The processing request failed. | 
+| NewSenderRegistering | New on-prem sender is registering. | 
+| ProcessingRequestFailed | The processing of a Hybrid Connection operation has failed. | 
 | SenderConnectionClosed | The sender connection is closed. |
-| SenderListenerConnectionEstablished | The sender and listener established connection. |
-| SenderSentHttpRequest | The sender sent HTTP request. | 
+| SenderListenerConnectionEstablished | The sender and listener established connection successfully. |
+| SenderSentHttpRequest | The sender sent an HTTP request. | 
 
 
 ## Next steps