Skip to content

Commit 9859d8a

Browse files
Merge pull request #295120 from amagginetti/patch-32
Update call-summary-updates-log-schema.md
2 parents 6b25085 + a3b1082 commit 9859d8a

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ When using the Call Diagnostics Updates Log Schema, always refer to the highest
4242

4343
### More about log versions and data latency
4444

45+
The call diagnostics updates log schema may require approximately 60 minutes following the end of a call to propogate data, most logs may be available within 40 minutes.
46+
4547
After a call ends, an initial version (version 1) of the log is sent to the CallSummaryUpdates and CallDiagnosticUpdates tables. Initial versions may contain `null` values, if more information becomes available updated versions of the logs are created with more complete information. For example, client data can be delayed because of network connectivity issues between the client computer and our servers, or something as simple as a user closing the lid on their laptop post-call before their client data was sent and re-opening it hours (or days) later.
4648

4749

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@ When using the call summary updates log schema, always refer to the highest `Cal
4343

4444
### More about log versions and data latency
4545

46+
The call summary updates log schema may require approximately 60 minutes following the end of a call to propogate data, most logs may be available within 40 minutes.
47+
4648
After a call ends, an initial version (version 1) of the log is sent to the CallSummaryUpdates and CallDiagnosticUpdates tables. Initial versions may contain `null` values, if more information becomes available updated versions of the logs are created with more complete information. For example, client data can be delayed because of network connectivity issues between the client computer and our servers, or something as simple as a user closing the lid on their laptop post-call before their client data was sent and re-opening it hours (or days) later.
4749

4850

@@ -355,4 +357,4 @@ If you have multiple Azure Communications Services resource IDs, you must enable
355357
- Learn about the [insights dashboard to monitor Voice Calling and Video Calling logs](/azure/communication-services/concepts/analytics/insights/voice-and-video-insights).
356358

357359
- Learn how to use call logs to diagnose call quality and reliability
358-
issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
360+
issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)

0 commit comments

Comments
 (0)