Skip to content

Evidence Map

This guide maps failure types to the specific metrics, logs, and configurations needed for effective troubleshooting.

Evidence Collection by Failure Type

Failure Type Metrics Log Analytics Tables Event Grid Events
SMS Delivery SmsMessagesSent, SmsMessagesDelivered ACSIncomingSMSEvents, ACSSMSDeliveryReportEvents Microsoft.Communication.SMSReceived, Microsoft.Communication.SMSDeliveryReportReceived
Email Delivery EmailMessagesSent, EmailMessagesDelivered ACSEmailDeliveryReportEvents Microsoft.Communication.EmailDeliveryReportReceived
Chat Latency ChatMessageReceived, ChatMessageSent ACSChatMessageReceivedEvents, ACSChatMessageSentEvents Microsoft.Communication.ChatMessageReceived
Call Quality CallMediaStreamQuality, CallMediaSetup ACSCallSummaryEvents, ACSCallDiagnosticsEvents Microsoft.Communication.CallStarted, Microsoft.Communication.CallEnded
Teams Interop TeamsInteroperabilityEvents ACSTeamsInteroperabilityEvents Microsoft.Communication.TeamsMeetingParticipantAdded

Evidence Types

1. Azure Monitor Metrics

Provide real-time visibility into service health, error rates, and throughput. Essential for alerting.

2. Log Analytics

Provide granular transaction-level details, error codes, and request/response metadata. Best for retrospective root cause analysis.

3. ACS Client Diagnostics

Client-side logs and User Facing Diagnostics (UFD) provide insights into network conditions and device issues.

4. Event Grid

Real-time webhooks for delivery reports, message events, and state changes.

Evidence Flow

graph TD
    Symptom[Observed Symptom] --> Metrics[Check Azure Monitor Metrics]
    Metrics -- Pattern Found? --> Alert[Identify Affected Service]
    Alert --> Logs[Query Log Analytics]
    Logs -- Transaction Details? --> RC[Confirm Root Cause]
    RC --> Event[Verify Event Grid Delivery Reports]

See Also

Sources