add callback metric

Author: fangchen0601

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

@@ -16,18 +16,26 @@ Azure Communication Services currently provides metrics for all Communication Se
 
 ## Where to find metrics
 
-Primitives in Communication Services emit metrics for API requests. To find these metrics, see the **Metrics** tab under your Communication Services resource. You can also create permanent dashboards by using the workbooks tab under your Communication Services resource.
+Primitives in Communication Services emit metrics for API requests and callback events. To find these metrics, see the **Metrics** tab under your Communication Services resource. You can also create permanent dashboards by using the workbooks tab under your Communication Services resource.
 
 ## Metric definitions
 
-All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
-
-For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](/azure/azure-monitor/essentials/metrics-charts#aggregation).
-
-- **Operation**: All operations or routes that can be called on the Communication Services Chat gateway.
+All API request metrics contain three dimensions that you can use to filter your metrics data.
+- **Operation**: All operations or routes that can be called on the Communication Services CallAutomation.
 - **Status Code**: The status code response sent after the request.
 - **StatusSubClass**: The status code series sent after the response.
 
+The callback event metrics contains those dimensions that you can use to filter your metrics data. 
+- **EventTypeName**: The callback event type name.
+- **Code**: The status code of the callback event.
+- **CodeClass**: The status code series of the callback event.
+- **SubCode**: The sub code of the callback event.
+- **Version**: The version of the callback event.
+
+These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
+
+For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](/azure/azure-monitor/essentials/metrics-charts#aggregation).
+
 ### Call Automation API requests
 
 The following operations are available on Call Automation API request metrics.
@@ -52,6 +60,51 @@ The following operations are available on Call Automation API request metrics.
 | Delete Call           | Delete a call.    |
 | Cancel All Media Operations | Cancel all ongoing or queued media operations in a call. |
 
+### Call Automation Callback Event
+
+The following event type name are available on Call Automation Callback Event metrics.
+
+| Event Type Name                                   |
+| ------------------------------------------------- |
+| Microsoft.Communication.AddParticipantFailed      |
+| Microsoft.Communication.AddParticipantSucceeded   |
+| Microsoft.Communication.AnswerCallFailed          |
+| Microsoft.Communication.CallConnected             |
+| Microsoft.Communication.CallDisconnected          |
+| Microsoft.Communication.CallTransferAccepted      |
+| Microsoft.Communication.CallTransferFailed        |
+| Microsoft.Communication.CancelAddParticipantFailed|
+| Microsoft.Communication.CancelAddParticipantSucceeded |
+| Microsoft.Communication.ConnectFailed             |
+| Microsoft.Communication.ContinuousDtmfRecognitionStopped |
+| Microsoft.Communication.ContinuousDtmfRecognitionToneFailed |
+| Microsoft.Communication.ContinuousDtmfRecognitionToneReceived |
+| Microsoft.Communication.CreateCallFailed          |
+| Microsoft.Communication.HoldFailed                |
+| Microsoft.Communication.MediaStreamingFailed      |
+| Microsoft.Communication.MediaStreamingStarted     |
+| Microsoft.Communication.MediaStreamingStopped     |
+| Microsoft.Communication.ParticipantsUpdated       |
+| Microsoft.Communication.PlayCanceled              |
+| Microsoft.Communication.PlayCompleted             |
+| Microsoft.Communication.PlayFailed                |
+| Microsoft.Communication.PlayStarted               |
+| Microsoft.Communication.RecordingStateChanged     |
+| Microsoft.Communication.RecognizeCanceled         |
+| Microsoft.Communication.RecognizeCompleted        |
+| Microsoft.Communication.RecognizeFailed           |
+| Microsoft.Communication.RemoveParticipantFailed   |
+| Microsoft.Communication.RemoveParticipantSucceeded |
+| Microsoft.Communication.SendDtmfTonesCompleted    |
+| Microsoft.Communication.SendDtmfTonesFailed       |
+| Microsoft.Communication.TranscriptionFailed       |
+| Microsoft.Communication.TranscriptionStarted      |
+| Microsoft.Communication.TranscriptionStopped      |
+| Microsoft.Communication.TranscriptionUpdated      |
+
+The Code and SubCode values within the ResultInformation of a callback event indicate the status of an operation. These values are identical and can be used to determine the reason for an event, such as a call being disconnected. For details on specific disconnection reasons, refer to the list of codes provided at [Call end troubleshooting codes](../../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md?pivots=callend).
+
+
 ## Next steps
 
 Learn more about [Data Platform Metrics](/azure/azure-monitor/essentials/data-platform-metrics).