You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/analytics/call-logs-azure-monitor.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ The Call Summary Log contains data to help you identify key properties of all Ca
77
77
| operationVersion | The api-version associated with the operation, if the `operationName` was performed using an API. If there is no API that corresponds to this operation, the version represents the version of that operation in case the properties associated with the operation change in the future. |
78
78
| category | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the `properties` blob of an event are the same within a particular log category and resource type. |
79
79
| correlationIdentifier |`correlationIdentifier` is the unique ID for a Call. The `correlationIdentifier` identifies correlated events from all of the participants and endpoints that connect during a single Call, and it can be used to join data from different logs. If you ever need to open a support case with Microsoft, the `correlationID` will be used to easily identify the Call you're troubleshooting. |
80
-
| identifier | This is the unique ID for the user, matching the identity assigned by the Communications Authentication service. You can use this ID to correlate user events across different logs. This ID can also be used to identify Microsoft Teams "Interoperability" scenarios described later in this document. |
80
+
| identifier | This is the unique ID for the user. The identity can be an Azure Communications Services user, Azure AD user ID, Teams anonymous user ID or Teams bot ID. You can use this ID to correlate user events across different logs.|
81
81
| callStartTime | A timestamp for the start of the call, based on the first attempted connection from any Endpoint. |
82
82
| callDuration | The duration of the Call expressed in seconds, based on the first attempted connection and end of the last connection between two endpoints. |
83
83
| callType | Will contain either `"P2P"` or `"Group"`. A `"P2P"` Call is a direct 1:1 connection between only two, non-server endpoints. A `"Group"` Call is a Call that has more than two endpoints or is created as `"Group"` Call prior to the connection. |
@@ -102,7 +102,7 @@ Call Diagnostic Logs provide important information about the Endpoints and the m
102
102
| category | The log category of the event. Category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the `properties` blob of an event are the same within a particular log category and resource type. |
103
103
| correlationIdentifier | The `correlationIdentifier` identifies correlated events from all of the participants and endpoints that connect during a single Call. `correlationIdentifier` is the unique ID for a Call. If you ever need to open a support case with Microsoft, the `correlationID` will be used to easily identify the Call you're troubleshooting. |
104
104
| participantId | This ID is generated to represent the two-way connection between a "Participant" Endpoint (`endpointType` = `“Server”`) and the server. When `callType` = `"P2P"`, there is a direct connection between two endpoints, and no `participantId` is generated. |
105
-
| identifier | This ID represents the useridentity, as defined by the Authentication service. Use this ID to correlate different events across calls and services. |
105
+
| identifier | This is the unique ID for the user. The identity can be an Azure Communications Services user, Azure AD user ID, Teams anonymous user ID or Teams bot ID. You can use this ID to correlate user events across different logs.|
106
106
| endpointId | Unique ID that represents each Endpoint connected to the call, with Endpoint type defined by `endpointType`. When the value is `null`, it means that the connected entity is the Communication Services server. `EndpointId` can persist for the same user across multiple calls (`correlationIdentifier`) for native clients but will be unique for every Call when the client is a web browser. |
107
107
| endpointType | This value describes the properties of each `endpointId`. Can contain `“Server”`, `“VOIP”`, `“PSTN”`, `“BOT”`, or `“Unknown”`. |
108
108
| mediaType | This string value describes the type of media being transmitted between endpoints within each stream. Possible values include `“Audio”`, `“Video”`, `“VBSS”` (Video-Based Screen Sharing), and `“AppSharing”`. |
@@ -408,4 +408,4 @@ Diagnostic log for audio stream from Server Endpoint to VoIP Endpoint 3:
0 commit comments