Skip to content

Commit fdc6010

Browse files
committed
tables
1 parent 21eb1cf commit fdc6010

File tree

7 files changed

+22
-0
lines changed

7 files changed

+22
-0
lines changed

articles/communication-services/concepts/analytics/logs/call-client-media-statistics-log-schema.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,9 @@ Diagnostics for your Azure Communication Services Resource. [Learn more about Ca
3434
3535
## Log structure
3636

37+
The table below describes each property.
38+
39+
3740
| Property | Description |
3841
|--- |--- |
3942
| `OperationName` | The operation associated with the log record. |

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,9 @@ This log provides detailed information on actions taken during a call and can be
2525
2626
## Log structure
2727

28+
The table below describes each property.
29+
30+
2831
| Property | Description |
2932
|--- |--- |
3033
| `CallClientTimeStamp` | The timestamp for when on operation occurred on the SDK in UTC. |

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,9 @@ For each endpoint within a call, a distinct call diagnostic log is created for o
2727
2828
## Log structure
2929

30+
The table below describes each property.
31+
32+
3033
| Property | Description |
3134
|--- |--- |
3235
| `operationName` | The operation associated with the log record. |

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,16 @@ ms.service: azure-communication-services
1212
ms.subservice: calling
1313
---
1414

15+
This document is intended as a reference for the ACSCallingMetrics logs. Use these logs to gain a clearer understanding of daily aggregated calling metrics across various dimensions for your communication workloads.
16+
1517
# Call Metrics Log Schema
1618

1719
This log contains aggregated calling metrics in daily bins based on attributes such as SDK Version, OS name, and Error Subcode. These logs are used in the **[Voice and video Insights Dashboard](../insights/voice-and-video-insights.md)** to visualize long term graphs of reliability, quality, and performance based on count of succeeded and failed Calling SDK api calls of various operations. You can also set up automated alerts when a metric falls. **ankesh please explain how to do alerts**
1820

1921
EXPLAIN METRICS CONCEPTUALLY
2022

23+
24+
2125
a separate page that explains "metrics" conceptually
2226
what is metric - Based on thresholds defined in ACSCallingMetrics.Goal how many distinct api calls succeded or failed in a daily bucket for dimentions liek SDK version, make model, subcode etc
2327
what does it measure - Failure and success count for a particualr api call or a complex condition like UFD recovering (count of good UFD>= count of bad UFD)
@@ -32,6 +36,7 @@ failure - an api call failing with unexpected error or a complex condition faili
3236
3337
## Log structure
3438

39+
The table below describes each property.
3540

3641
| Property | Description |
3742
|----------------------------|----------------------------------------------------------------------------------------------------------------------------|

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ The call summary log contains data to help you identify key properties of all ca
2828
> [!IMPORTANT]
2929
> Participant information in the call summary log varies based on the participant tenant. The SDK version and OS version are redacted if the participant is not within the same tenant (also called *cross-tenant*) as the Communication Services resource. Cross-tenant participants are classified as external users invited by a resource tenant to join and collaborate during a call.
3030
31+
The table below describes each property.
32+
3133
| Property | Description |
3234
|--- |--- |
3335
| `time` | The time stamp (UTC) when the log was generated. |

articles/communication-services/concepts/analytics/logs/end-of-call-survey-logs.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,9 @@ Communication Services offers the following types of logs that you can enable:
5656

5757
## **Properties** ##
5858

59+
The table below describes each property.
60+
61+
5962
| Property | Description |
6063
| -------- | ---------------|
6164
|`Timegenerated` | This field represents the timestamp (UTC) of when the log was generated|

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ The usage log schema is used to.....
2222
2323
## Log structure
2424

25+
The table below describes each property.
26+
27+
2528
| Property | Description |
2629
| -------- | ---------------|
2730
| `Timestamp` | The time stamp (UTC) when the log was generated. |

0 commit comments

Comments
 (0)