Skip to content

Commit bbcdb3c

Browse files
authored
Create monitoring-logs-and-metrics.md
1 parent 3106df9 commit bbcdb3c

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Azure logs and metrics for Teams external users
3+
titleSuffix: An Azure Communication Services concept document
4+
description: Azure logs and metrics emitted for Teams external users
5+
author: tomaschladek
6+
ms.author: tchladek
7+
ms.date: 12/9/2022
8+
ms.topic: conceptual
9+
ms.service: azure-communication-services
10+
ms.subservice: teams-interop
11+
---
12+
13+
# Monitor Logs for Teams external users
14+
15+
In this article, you will learn which Azure logs and metrics are emitted for Teams external users when joining Teams meetings. Azure Communication Services user joining Teams meeting emits the following metrics: [Authentication API](./../metrics#authentication-api-requests) and [Chat API](./../metrics#chat-api-request-metric-operations). Communication Services resource additionally tracks the following logs: [Call Summary](./../analytics/call-logs-azure-monitor#call-summary-log) and [Call Diagnostic](./../analytics/call-logs-azure-monitor#call-diagnostic-log) Log.
16+
17+
Authentication API metrics emit records for every operation called on the Identity SDK or API (for example, creating a user `CreateIdentity` or issue of a token `CreateToken`). Chat API metrics emit records for every chat API call made via chat SDKs or APIs (for example, creating a thread or sending a message).
18+
19+
20+
Call summary and call diagnostics logs are emitted only for the following participants of the meeting:
21+
- Organizer of the meeting if actively joined the meeting
22+
- Azure Communication Services users joining the meeting from the same tenant (even when in the lobby)
23+
- Additional Teams users joining the meeting only if the organizer and current Azure Communication Services resource are in the same tenant
24+
- Bots
25+
- Phone number legs
26+
27+
If Azure Communication Services resource and Teams meeting organizer tenants are different, then some fields of the logs are redacted. You can find more information in the call summary & diagnostics logs [documentation](./../analytics/call-logs-azure-monitor.md).
28+
29+
## Bots
30+
Bots indicate service logic provided during the meeting. Here is a list of frequently used bots:
31+
- b1902c3e-b9f7-4650-9b23-5772bd429747 - Teams convenient recording
32+
33+
## Next steps
34+
35+
- [Enable logs and metrics](./../analytics/enable-logging.md)
36+
- [Metrics](./../metrics.md)
37+
- [Call summary and call diagnostics](./../analytics/call-logs-azure-monitor.md)

0 commit comments

Comments
 (0)