update

Author: amagginetti

articles/communication-services/concepts/analytics/logs/call-client-media-statistics-log-schema.md

@@ -21,26 +21,30 @@ data on the audio, video, and screen share media steams between
 participants with a default 10-seconds aggregation interval. The logs contain granular time series information about media stream type, direction, codec, and bitrate properties (for example, max, min, average).
 
 
-This log provides more detailed information than the Call Diagnostic log
+This log provides more detailed information than the Call Diagnostics log
 to understand the quality of media steams between participants. It can be used to
 visualize and investigate quality issues for your calls through Call
 Diagnostics for your Azure Communication Services Resource. [Learn more about Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
 
 
+## Data Concepts
+
 > [!IMPORTANT]
 >You must collect logs if you want to analyze them. To learn more see: **[How do I store logs?](#how-do-i-store-logs)**
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
-## Log structure
+## Data Definitions
+
+### Call client metrics log schema
 
 The table below describes each property.
 
 
 | Property | Description |
 |--- |--- |
 | `OperationName` | The operation associated with the log record. |
-| `CallId` | The unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call, and you can use it to join data from different logs. It's similar to the correlationId in call summary log and call diagnostic log. |
+| `CallId` | The unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call, and you can use it to join data from different logs. It's similar to the correlationId in call summary log and call diagnostics log. |
 | `CallClientTimeStamp` | The timestamp when the media stats is recorded. |
 | `MetricName` | The name of the media statistics, such as `Bitrate`, `JitterInMs`, `PacketsPerSecond`, and so on.  |
 | `Count`| The number of data points sampled at a given timestamp. |

articles/communication-services/concepts/analytics/logs/call-client-operations-log-schema.md

@@ -14,16 +14,21 @@ ms.subservice: calling
 
 # Call Client Operations Log Schema
 
+
 The **call client operations** log provides client-side information about the calling endpoints and participants involved in a call. These logs are currently in preview and show client events that occurred in a call and which actions a customer takes during a call.  
 
 This log provides detailed information on actions taken during a call and can be used to visualize and investigate call issues by using Call Diagnostics for your Azure Communication Services Resource. [Learn more about Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
 
+## Data Concepts
+
 > [!IMPORTANT]
 >You must collect logs if you want to analyze them. To learn more see: **[How do I store logs?](#how-do-i-store-logs)**
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
-## Log structure
+## Data Definitions
+
+### Call client operations log schema
 
 The table below describes each property.
 
@@ -32,7 +37,7 @@ The table below describes each property.
 |--- |--- |
 |     `CallClientTimeStamp`         |     The timestamp for when on operation occurred on the SDK in UTC.   |
 |     `OperationName`         |    The name of the operation triggered on the calling SDK.   |
-|     `CallId`    |              The unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call, and you can use it to join data from different logs. It's similar to the correlationId in call summary log and call diagnostic log.               |
+|     `CallId`    |              The unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call, and you can use it to join data from different logs. It's similar to the correlationId in call summary log and call diagnostics log.               |
 |     `ParticipantId`    |            The unique identifier for each call leg (in Group calls) or call participant (in Peer to Peer calls). This ID is the main correlation point between CallSummary, CallDiagnostic, CallClientOperations, and CallClientMediaStats logs.             |
 |     `OperationType`    |              Call Client Operation.               |
 |     `OperationId`    |             A unique GGUID identifying an SDK operation.                 |

articles/communication-services/concepts/analytics/logs/call-diagnostics-log-schema.md

@@ -1,7 +1,7 @@
 ---
-title: Azure Communication Services Call Diagnostic Log Schema
+title: Azure Communication Services Call Diagnostics Log Schema
 titleSuffix: An Azure Communication Services concept article
-description: Learn about the Voice and Video Call Diagnostic Logs.
+description: Learn about the Voice and Video Call Diagnostics Logs.
 author:  amagginetti
 services: azure-communication-services
 
@@ -12,20 +12,23 @@ ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
-# Call Diagnostic Log Schema
+# Call Diagnostics Log Schema
 
 
-Call diagnostic logs provide important information about the endpoints and the media transfers for each participant. They also provide measurements that help you understand quality problems.
+Call diagnostics logs provide important information about the endpoints and the media transfers for each participant. They also provide measurements that help you understand quality problems.
 
-For each endpoint within a call, a distinct call diagnostic log is created for outbound media streams (audio or video, for example) between endpoints. In a P2P call, each log contains data that relates to each of the outbound streams associated with each endpoint. In group calls, `participantId` serves as a key identifier to join the related outbound logs into a distinct participant connection. Call diagnostic logs remain intact and are the same regardless of the participant tenant.
+For each endpoint within a call, a distinct call diagnostics log is created for outbound media streams (audio or video, for example) between endpoints. In a P2P call, each log contains data that relates to each of the outbound streams associated with each endpoint. In group calls, `participantId` serves as a key identifier to join the related outbound logs into a distinct participant connection. Call diagnostics logs remain intact and are the same regardless of the participant tenant.
 
+## Data Concepts
 
 > [!IMPORTANT]
 >You must collect logs if you want to analyze them. To learn more see: **[How do I store logs?](#how-do-i-store-logs)**
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
-## Log structure
+## Data Definitions
+
+### Call diagnostics log schema
 
 The table below describes each property.
 
@@ -77,17 +80,17 @@ Here are shared fields for all logs in a P2P call:
 "correlationId":            "aaaa0000-bb11-2222-33cc-444444dddddd",
 ```
 
-#### Call diagnostic logs 
+#### Call diagnostics logs 
 
-Call diagnostic logs share operation information:
+Call diagnostics logs share operation information:
 
 ```json
 "operationName":            "CallDiagnostics",
 "operationVersion":         "1.0",
 "category":                 "CallDiagnostics",
 ```
 
-Here's a diagnostic log for an audio stream from VoIP endpoint 1 to VoIP endpoint 2:
+Here's a diagnostics log for an audio stream from VoIP endpoint 1 to VoIP endpoint 2:
 
 ```json
 "properties": {
@@ -107,7 +110,7 @@ Here's a diagnostic log for an audio stream from VoIP endpoint 1 to VoIP endpoin
 }
 ```
 
-Here's a diagnostic log for an audio stream from VoIP endpoint 2 to VoIP endpoint 1:
+Here's a diagnostics log for an audio stream from VoIP endpoint 2 to VoIP endpoint 1:
 
 ```json
 "properties": {
@@ -127,7 +130,7 @@ Here's a diagnostic log for an audio stream from VoIP endpoint 2 to VoIP endpoin
 }
 ```
 
-Here's a diagnostic log for a video stream from VoIP endpoint 1 to VoIP endpoint 2:
+Here's a diagnostics log for a video stream from VoIP endpoint 1 to VoIP endpoint 2:
 
 ```json
 "properties": {
@@ -149,7 +152,7 @@ Here's a diagnostic log for a video stream from VoIP endpoint 1 to VoIP endpoint
 
 ### Group call
 
-Data for a group call is generated in three call summary logs and six call diagnostic logs. Here are shared fields for all logs in the call:
+Data for a group call is generated in three call summary logs and six call diagnostics logs. Here are shared fields for all logs in the call:
 
 ```json
 "time":                     "2021-07-05T06:30:06.402Z",
@@ -159,17 +162,17 @@ Data for a group call is generated in three call summary logs and six call diagn
 
 
 
-#### Call diagnostic logs
+#### Call diagnostics logs
 
-Call diagnostic logs share operation information:
+Call diagnostics logs share operation information:
 
 ```json
 "operationName":            "CallDiagnostics",
 "operationVersion":         "1.0",
 "category":                 "CallDiagnostics",
 ```
 
-Here's a diagnostic log for an audio stream from VoIP endpoint 1 to a server endpoint:
+Here's a diagnostics log for an audio stream from VoIP endpoint 1 to a server endpoint:
 
 ```json
 "properties": {
@@ -189,7 +192,7 @@ Here's a diagnostic log for an audio stream from VoIP endpoint 1 to a server end
 }
 ```
 
-Here's a diagnostic log for an audio stream from a server endpoint to VoIP endpoint 1:
+Here's a diagnostics log for an audio stream from a server endpoint to VoIP endpoint 1:
 
 ```json
 "properties": {
@@ -209,7 +212,7 @@ Here's a diagnostic log for an audio stream from a server endpoint to VoIP endpo
 }
 ```
 
-Here's a diagnostic log for an audio stream from VoIP endpoint 3 to a server endpoint:
+Here's a diagnostics log for an audio stream from VoIP endpoint 3 to a server endpoint:
 
 ```json
 "properties": {
@@ -229,7 +232,7 @@ Here's a diagnostic log for an audio stream from VoIP endpoint 3 to a server end
 }
 ```
 
-Here's a diagnostic log for an audio stream from a server endpoint to VoIP endpoint 3:
+Here's a diagnostics log for an audio stream from a server endpoint to VoIP endpoint 3:
 
 ```json
 "properties": {

articles/communication-services/concepts/analytics/logs/call-metrics-log-schema.md

@@ -12,13 +12,16 @@ ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
-This document is intended as a reference for the ACSCallingMetrics logs. Use these logs to gain a clearer understanding of daily aggregated calling metrics across various dimensions for your communication workloads.
 
 # Call Metrics Log Schema
 
-This log contains aggregated calling metrics in daily bins based on attributes such as SDK Version, OS name, and Error Subcode. These logs are used in the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** to visualize long term graphs of reliability, quality, and performance based on count of succeeded and failed Calling SDK api calls of various operations. You can also set up automated alerts when a metric falls. **ankesh please explain how to do alerts**
+This document explains the ACSCallingMetrics logs available to you through Azure Monitor in the form of [Resource Logs](/azure/azure-monitor/data-sources.md#azure-resources). 
 
-EXPLAIN METRICS CONCEPTUALLY
+Call Metrics logs are used in the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** to visualize long term graphs of reliability, quality, and performance based on count of succeeded and failed Calling SDK api calls of various operations. Use these logs to gain a clearer understanding of daily aggregated calling metrics across various dimensions for your communication workloads. You can also set up automated alerts when a metric falls. **ankesh please explain how to do alerts**
+
+Call Metrics logs contain aggregated calling metrics in daily bins based on attributes such as SDK Version, OS name, and Error Subcode.
+
+## Data Concepts
 
 
 
@@ -34,7 +37,9 @@ failure - an api call failing with unexpected error or a complex condition faili
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
-## Log structure
+## Data Definitions
+
+### Call metrics log schema
 
 The table below describes each property.
 

articles/communication-services/concepts/analytics/logs/call-summary-log-schema.md

@@ -17,13 +17,17 @@ ms.subservice: calling
 The call summary log contains data to help you identify key properties of all calls. A different call summary log is created for each `participantId` (or `endpointId` for peer-to-peer [P2P] calls) value in the call.
 
 
+## Data Concepts
+
 > [!IMPORTANT]
 >You must collect logs if you want to analyze them. To learn more see: **[How do I store logs?](#how-do-i-store-logs)**
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
 
-## Log Structure
+## Data Definitions
+
+### Call summary log schema
 
 > [!IMPORTANT]
 > Participant information in the call summary log varies based on the participant tenant. The SDK version and OS version are redacted if the participant is not within the same tenant (also called *cross-tenant*) as the Communication Services resource. Cross-tenant participants are classified as external users invited by a resource tenant to join and collaborate during a call.
@@ -172,7 +176,7 @@ Here's a call summary for a PSTN call:
 ```
 ### Group calls 
 
-Data for a group call is generated in three call summary logs and six call diagnostic logs. Here are shared fields for all logs in the call:
+Data for a group call is generated in three call summary logs and six call diagnostics logs. Here are shared fields for all logs in the call:
 
 ```json
 "time":                     "2021-07-05T06:30:06.402Z",

articles/communication-services/concepts/analytics/logs/end-of-call-survey-logs.md

@@ -49,6 +49,7 @@ In addition to the above, the optional tags in the responses offer further insig
 
 By analyzing the data captured in the End of Call Survey logs, you can pinpoint areas that require improvement, thereby enhancing the overall user experience. 
 
+
 ## Resource log categories
 
 Communication Services offers the following types of logs that you can enable:

articles/communication-services/concepts/analytics/logs/usage-log-schema.md

@@ -15,12 +15,16 @@ ms.subservice: calling
 # Usage Log Schema
 The usage log schema is used to.....
 
+## Data Concepts
+
 > [!IMPORTANT]
 >You must collect logs if you want to analyze them. To learn more see: **[How do I store logs?](#how-do-i-store-logs)**
 >
 >Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data is not retroactively available. You accumulate data once you set up the Diagnostic Settings.
 
-## Log structure
+## Data Definitions
+
+### Usage log schema
 
 The table below describes each property.