Skip to content

Commit e087591

Browse files
committed
edit pass: recording-logs
1 parent 4b02c5d commit e087591

File tree

1 file changed

+43
-35
lines changed

1 file changed

+43
-35
lines changed

articles/communication-services/concepts/analytics/recording-logs.md

Lines changed: 43 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Azure Communication Services - Recording Analytics Public Preview
3-
titleSuffix: An Azure Communication Services concept document
4-
description: About using Log Analytics for recording logs
2+
title: Call Recording summary logs
3+
titleSuffix: An Azure Communication Services conceptual article
4+
description: Learn about using Log Analytics for recording logs.
55
author: Mkhribech
66
services: azure-communication-services
77

@@ -12,50 +12,55 @@ ms.service: azure-communication-services
1212
ms.subservice: data
1313
---
1414

15-
# Call Recording Summary Log
16-
Call recording summary logs provide details about the call duration, media content (e.g., Audio-Video, Unmixed, Transcription, etc.), the format types used for the recording (e.g., WAV, MP4, etc.), as well as the reason of why the recording ended.
15+
# Call Recording summary logs
16+
In Azure Communication Services, summary logs for the Call Recording feature provide details about:
1717

18-
Recording file is generated at the end of a call or meeting. The recording can be initiated and stopped by either a user or an app (bot) or ended due to a system failure.
18+
- Call duration.
19+
- Media content (for example, audio/video, unmixed, or transcription).
20+
- The format types used for the recording (for example, WAV or MP4).
21+
- The reason why the recording ended.
1922

20-
> [!IMPORTANT]
23+
A recording file is generated at the end of a call or meeting. The recording can be initiated and stopped by either a user or an app (bot). It can also end because of a system failure.
2124

22-
> Please note the call recording logs will be published once the call recording is ready to be downloaded. The log will be published within the standard latency time for Azure Monitor Resource logs see [Log data ingestion time in Azure Monitor](../../../azure-monitor/logs/data-ingestion-time.md#azure-metrics-resource-logs-activity-log)
25+
> [!IMPORTANT]
26+
> Summary logs are published after a recording is ready to be downloaded. The logs are published within the standard latency time for Azure Monitor resource logs. See [Log data ingestion time in Azure Monitor](../../../azure-monitor/logs/data-ingestion-time.md#azure-metrics-resource-logs-activity-log).
2327
2428

25-
## Properties Description
29+
## Properties
2630

27-
| Field Name | DataType | Description |
31+
| Property name | Data type | Description |
2832
|---------- |-----------|--------------|
29-
|timeGenerated|DateTime|The timestamp (UTC) of when the log was generated|
30-
|operationName| String | The operation associated with log record|
31-
|correlationId |String |`CallID` is used to correlate events between multiple tables|
32-
|recordingID| String | The ID given to the recording this log refers to|
33-
|category| String | The log category of the event. Logs with the same log category and resource type will have the same properties fields|
34-
|resultType| String| The status of the operation |
35-
|level |String |The severity level of the operation |
36-
|chunkCount |Integer|The total number of chunks created for the recording|
37-
|channelType| String |The recording's channel type, i.e., mixed, unmixed|
38-
|recordingStartTime| DateTime|The time that the recording started |
39-
|contentType| String | The recording's content, i.e., Audio Only, Audio - Video, Transcription, etc.|
40-
|formatType| String | The recording's file format |
41-
|recordingLength| Double | Duration of the recording in seconds |
42-
|audioChannelsCount| Integer | Total number of audio channels in the recording|
43-
|recordingEndReason| String | The reason why the recording ended |
44-
45-
46-
## Call recording and sample data
33+
|`timeGenerated`|DateTime|Time stamp (UTC) of when the log was generated.|
34+
|`operationName`|String|Operation associated with a log record.|
35+
|`correlationId`|String|ID that's used to correlate events between tables.|
36+
|`recordingID`|String|ID given to the recording that this log refers to.|
37+
|`category`|String|Log category of the event. Logs with the same log category and resource type have the same property fields.|
38+
|`resultType`|String| Status of the operation.|
39+
|`level`|String |Severity level of the operation.|
40+
|`chunkCount`|Integer|Total number of chunks created for the recording.|
41+
|`channelType`|String|Channel type of the recording, such as mixed or unmixed.|
42+
|`recordingStartTime`|DateTime|Time that the recording started.|
43+
|`contentType`|String|Content of the recording, such as audio only, audio/video, or transcription.|
44+
|`formatType`|String|File format of the recording.|
45+
|`recordingLength`|Double|Duration of the recording in seconds.|
46+
|`audioChannelsCount`|Integer|Total number of audio channels in the recording.|
47+
|`recordingEndReason`|String|Reason why the recording ended.|
48+
49+
## Call Recording and sample data
50+
4751
```json
4852
"operationName": "Call Recording Summary",
4953
"operationVersion": "1.0",
5054
"category": "RecordingSummaryPUBLICPREVIEW",
5155

5256
```
53-
A call can have one recording or many recordings depending on how many times a recording event is triggered.
57+
A call can have one recording or many recordings, depending on how many times a recording event is triggered.
58+
59+
For example, if an agent initiates an outbound call on a recorded line and the call drops because of a poor network signal, `callid` will have one `recordingid` value. If the agent calls back the customer, the system generates a new `callid` instance and a new `recordingid` value.
5460

55-
For example, if an agent initiates an outbound call in a recorded line and the call drops due to poor network signal, the `callid` will have one `recordingid`. If the agent calls back the customer, the system will generate a new `callid` as well as a new `recordingid`.
5661

62+
#### Example: Call Recording for one call to one recording
5763

58-
#### Example1: Call recording for "One call to one recording"
5964
```json
6065
"properties"
6166
{
@@ -77,9 +82,10 @@ For example, if an agent initiates an outbound call in a recorded line and the c
7782
}
7883
```
7984

80-
If the agent initiated a recording and stopped and restarted the recording multiple times while the call is still on, the `callid` will have many `recordingid` depending on how many times the recording events were triggered.
85+
If the agent initiates a recording and stops and restarts the recording multiple times while the call is still on, `callid` will have many `recordingid` values, depending on how many times the recording events were triggered.
86+
87+
#### Example: Call Recording for one call to many recordings
8188

82-
#### Example2: Call recording for "One call to many recordings"
8389
```json
8490

8591
{
@@ -117,6 +123,8 @@ If the agent initiated a recording and stopped and restarted the recording mult
117123
"AudioChannelsCount": 1
118124
}
119125
```
120-
See also call recording for more info
121-
[Azure Communication Services Call Recording overview](../../../communication-services/concepts/voice-video-calling/call-recording.md)
126+
127+
## Next steps
128+
129+
For more information about Call Recording, see [Call Recording overview](../../../communication-services/concepts/voice-video-calling/call-recording.md).
122130

0 commit comments

Comments
 (0)