Skip to content

Commit b0bc68e

Browse files
committed
new "updates" pages
1 parent 0862dba commit b0bc68e

File tree

5 files changed

+637
-11
lines changed

5 files changed

+637
-11
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,9 @@ ms.subservice: calling
1717

1818
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.
1919

20-
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.
20+
For each `EndpointId` within a call (including the server), Azure Communication Services creates a distinct call diagnostics log for each media stream (audio or video, for example) between endpoints.
21+
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.
22+
2123

2224
## Data Concepts
2325

0 commit comments

Comments
 (0)