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
The Billing Usage log schema give an overview of the different services you use.
15
+
# Billing usage log schema
16
+
The billing usage log schema give an overview of the different services you use.
17
17
18
-
## Data Concepts
18
+
## Data concepts
19
19
20
20
> [!IMPORTANT]
21
21
>You must collect logs if you want to analyze them. To learn more, see: **[How do I store logs?](#how-do-i-store-logs)**
22
22
>
23
23
>Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data isn't retroactively available. You accumulate data once you create the Diagnostic Settings.
24
24
25
-
## Data Definitions
25
+
## Data definitions
26
26
27
-
### Usage log schema
27
+
### Billing usage log schema
28
28
29
29
This table describes each property.
30
30
@@ -48,7 +48,7 @@ This table describes each property.
48
48
### How do I store logs?
49
49
The following section explains this requirement.
50
50
51
-
Azure Communication Services logs are not stored in your Azure account by default so you need to begin storing them in order for tools like [Voice and video Insights Dashboard](../insights/voice-and-video-insights.md) and [Call Diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
51
+
Azure Communication Services logs aren't stored in your Azure account by default so you need to begin storing them in order for tools like [voice and video insights dashboard](../insights/voice-and-video-insights.md) and [call diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
52
52
53
53
**Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.**
54
54
@@ -60,10 +60,6 @@ If you have multiple Azure Communications Services resource IDs, you must enable
60
60
61
61
## Next steps
62
62
63
-
- Review the overview of all Voice and Video logs, see: [Overview of Azure Communication Services Voice Calling and Video Call logs](voice-and-video-logs.md)
64
-
65
-
- Learn best practices to manage your call quality and reliability, see: [Improve and manage call quality](../../voice-video-calling/manage-call-quality.md)
66
-
67
63
- Learn about the [insights dashboard to monitor Voice Calling and Video Calling logs](/azure/communication-services/concepts/analytics/insights/voice-and-video-insights).
68
64
69
65
- Learn how to use call logs to diagnose call quality and reliability
# Call Client Media Statistics Time Series Log Schema
15
+
# Call client media statistics time series log schema
16
16
17
17
The **call client media statistics time series** log provides
18
18
client-side information about the media streams between individual
@@ -21,33 +21,33 @@ data on the audio, video, and screen share media steams between
21
21
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).
22
22
23
23
24
-
This log provides more detailed information than the Call Diagnostics log
24
+
This log provides more detailed information than the call diagnostics log
25
25
to understand the quality of media steams between participants. It can be used to
26
-
visualize and investigate quality issues for your calls through Call
27
-
Diagnostics for your Azure Communication Services Resource. [Learn more about Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
26
+
visualize and investigate quality issues for your calls through call
27
+
diagnostics for your Azure Communication Services Resource. [Learn more about call diagnostics](../../voice-video-calling/call-diagnostics.md)
28
28
29
29
30
-
## How to use Call Logs
30
+
## How to use call logs
31
31
We recommend you collect all available call logs in a log analytics resource so you can monitor your call usage and improve your call quality and receive new logs from Azure Communication Services as we release them.
32
32
33
33
There are two main tools you can use to monitor your calls and improve call quality.
34
-
1.[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)
We recommend using the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** dashboards to start
38
-
any quality investigations, and using **[Call Diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
37
+
We recommend using the **[voice and video insights dashboard](../insights/voice-and-video-insights.md)** dashboards to start
38
+
any quality investigations, and using **[call diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
39
39
40
40
41
-
## Data Concepts
41
+
## Data concepts
42
42
43
43
> [!IMPORTANT]
44
44
>You must collect logs if you want to analyze them. To learn more, see: **[How do I store logs?](#how-do-i-store-logs)**
45
45
>
46
46
>Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data isn't retroactively available. You accumulate data once you create the Diagnostic Settings.
47
47
48
-
## Data Definitions
48
+
## Data definitions
49
49
50
-
### Call client metrics log schema
50
+
### Call client media statistics time series log schema
51
51
52
52
This table describes each property.
53
53
@@ -117,7 +117,7 @@ Each participant can have many different media statistics metrics for a call. Th
117
117
### How do I store logs?
118
118
The following section explains this requirement.
119
119
120
-
Azure Communication Services logs are not stored in your Azure account by default so you need to begin storing them in order for tools like [Voice and video Insights Dashboard](../insights/voice-and-video-insights.md) and [Call Diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
120
+
Azure Communication Services logs aren't stored in your Azure account by default so you need to begin storing them in order for tools like [voice and video insights dashboard](../insights/voice-and-video-insights.md) and [call diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
121
121
122
122
**Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.**
123
123
@@ -129,7 +129,7 @@ If you have multiple Azure Communications Services resource IDs, you must enable
129
129
130
130
## Next steps
131
131
132
-
- Review the overview of all Voice and Video logs, see: [Overview of Azure Communication Services Voice Calling and Video Call logs](voice-and-video-logs.md)
132
+
- Review the overview of all voice and video logs, see: [Overview of Azure Communication Services call logs](voice-and-video-logs.md)
133
133
134
134
- Learn best practices to manage your call quality and reliability, see: [Improve and manage call quality](../../voice-video-calling/manage-call-quality.md)
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.
19
19
20
-
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)
20
+
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)
21
21
22
-
## How to use Call Logs
22
+
## How to use call logs
23
23
We recommend you collect all available call logs in a log analytics resource so you can monitor your call usage and improve your call quality and receive new logs from Azure Communication Services as we release them.
24
24
25
25
There are two main tools you can use to monitor your calls and improve call quality.
26
-
1.[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)
We recommend using the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** dashboards to start
30
-
any quality investigations, and using **[Call Diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
29
+
We recommend using the **[voice and video insights dashboard](../insights/voice-and-video-insights.md)** dashboards to start
30
+
any quality investigations, and using **[call diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
31
31
32
32
33
-
## Data Concepts
33
+
## Data concepts
34
34
35
35
> [!IMPORTANT]
36
36
>You must collect logs if you want to analyze them. To learn more, see: **[How do I store logs?](#how-do-i-store-logs)**
37
37
>
38
38
>Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data isn't retroactively available. You accumulate data once you create the Diagnostic Settings.
39
39
40
-
## Data Definitions
40
+
## Data definitions
41
41
42
42
### Call client operations log schema
43
43
@@ -98,7 +98,7 @@ Each participant can have many different metrics for a call. You can run the fol
98
98
### How do I store logs?
99
99
The following section explains this requirement.
100
100
101
-
Azure Communication Services logs are not stored in your Azure account by default so you need to begin storing them in order for tools like [Voice and video Insights Dashboard](../insights/voice-and-video-insights.md) and [Call Diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
101
+
Azure Communication Services logs aren't stored in your Azure account by default so you need to begin storing them in order for tools like [voice and video insights dashboard](../insights/voice-and-video-insights.md) and [call diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
102
102
103
103
**Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.**
104
104
@@ -110,7 +110,7 @@ If you have multiple Azure Communications Services resource IDs, you must enable
110
110
111
111
## Next steps
112
112
113
-
- Review the overview of all Voice and Video logs, see: [Overview of Azure Communication Services Voice Calling and Video Call logs](voice-and-video-logs.md)
113
+
- Review the overview of all voice and video logs, see: [Overview of Azure Communication Services call logs](voice-and-video-logs.md)
114
114
115
115
- Learn best practices to manage your call quality and reliability, see: [Improve and manage call quality](../../voice-video-calling/manage-call-quality.md)
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.
@@ -21,25 +21,25 @@ For each `EndpointId` within a call (including the server), Azure Communication
21
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
22
23
23
24
-
## How to use Call Logs
24
+
## How to use call logs
25
25
We recommend you collect all available call logs in a log analytics resource so you can monitor your call usage and improve your call quality and receive new logs from Azure Communication Services as we release them.
26
26
27
27
There are two main tools you can use to monitor your calls and improve call quality.
28
-
1.[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)
We recommend using the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** dashboards to start
32
-
any quality investigations, and using **[Call Diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
31
+
We recommend using the **[voice and video insights dashboard](../insights/voice-and-video-insights.md)** dashboards to start
32
+
any quality investigations, and using **[call diagnostics](../../voice-video-calling/call-diagnostics.md)** as needed to explore individual calls when you need granular detail.
33
33
34
34
35
-
## Data Concepts
35
+
## Data concepts
36
36
37
37
> [!IMPORTANT]
38
38
>You must collect logs if you want to analyze them. To learn more, see: **[How do I store logs?](#how-do-i-store-logs)**
39
39
>
40
40
>Azure doesn't store your call log data unless you enable these specific Diagnostic Settings. Your call data isn't retroactively available. You accumulate data once you create the Diagnostic Settings.
41
41
42
-
## Data Definitions
42
+
## Data definitions
43
43
44
44
### Call diagnostics log schema
45
45
@@ -268,7 +268,7 @@ Here's a diagnostics log for an audio stream from a server endpoint to VoIP endp
268
268
### How do I store logs?
269
269
The following section explains this requirement.
270
270
271
-
Azure Communication Services logs aren't stored in your Azure account by default so you need to begin storing them in order for tools like [Voice and video Insights Dashboard](../insights/voice-and-video-insights.md) and [Call Diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
271
+
Azure Communication Services logs aren't stored in your Azure account by default so you need to begin storing them in order for tools like [voice and video insights dashboard](../insights/voice-and-video-insights.md) and [call diagnostics](../../voice-video-calling/call-diagnostics.md) to work. To collect these call logs, you need to enable a diagnostic setting that directs the call data to a Log Analytics workspace.
272
272
273
273
**Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.**
274
274
@@ -280,7 +280,7 @@ If you have multiple Azure Communications Services resource IDs, you must enable
280
280
281
281
## Next steps
282
282
283
-
- Review the overview of all Voice and Video logs, see: [Overview of Azure Communication Services Voice Calling and Video Call logs](voice-and-video-logs.md)
283
+
- Review the overview of all voice and video logs, see: [Overview of Azure Communication Services call logs](voice-and-video-logs.md)
284
284
285
285
- Learn best practices to manage your call quality and reliability, see: [Improve and manage call quality](../../voice-video-calling/manage-call-quality.md)
0 commit comments