Skip to content
MS Teams Observability
Microsoft Teams logo

Home

Detect and resolve Microsoft Teams call issues faster with end-to-end observability from Graph API telemetry to operational dashboards.
Start in 15 min Browse Backends

MS Teams Observability is a collector + backend integration solution for Ops and IT teams: it pulls Microsoft Teams telemetry from Microsoft Graph and turns it into actionable dashboards and incident context in Dynatrace or Splunk.

What You Get

Section titled “What You Get”
  • Faster Incident Triage: correlate call degradations with Microsoft advisories and isolate impacted users or sites faster.
  • End-to-End Call Quality Visibility: track call quality from summary to stream-level metrics across users, devices, and networks.
  • Multi-Backend Ready: collect once and route telemetry to Dynatrace or Splunk based on your operating model.

Start in 15 Minutes

Section titled “Start in 15 Minutes”
  1. Check Prerequisites (Azure app, permissions, and network access).
  2. Deploy the Collector and run your first collection cycle.
  3. Connect your backend in Backends (Dynatrace or Splunk).
  4. Open dashboards and validate live quality and incident data.

How It Works

Section titled “How It Works”
flowchart LR
    A[Microsoft Graph API] --> B[MS Teams Observability Collector]
    B --> C[Dynatrace Backend]
    B --> D[Splunk Backend]
    C --> E[Dashboards and App Pages]
    D --> F[Dashboards and Searches]

One collector ingests Teams telemetry once and forwards it to your operational backend.

  1. Authenticate and collect: the collector uses your Azure app registration to call Microsoft Graph on a schedule.
  2. Normalize and enrich: records are transformed into consistent event families and enriched with context used for operations and troubleshooting.
  3. Export to one or more backends: the same collection cycle can send data to Dynatrace, Splunk, or both.
  4. Operate from dashboards and app pages: teams investigate degraded calls, impacted users/sites, and Microsoft advisories from a single workflow.

Typical telemetry available after ingestion includes:

  • Call metadata and stream quality indicators (for example RTT, jitter, and packet loss).
  • PSTN / Direct Routing / Auto Attendant / Call Queue data.
  • Microsoft service announcements and collector health signals.

Choose Your Backend

Section titled “Choose Your Backend”
Dynatrace Full integration with Grail, OpenPipeline, and a dedicated app for operations and troubleshooting.
Splunk HEC-based ingestion with a dedicated Splunk app and dashboards.

Visual Overview

Section titled “Visual Overview”
Dynatrace sites dashboard with call quality and site performance indicators
Example operational view: site and quality monitoring in Dynatrace.

Documentation by Task

Section titled “Documentation by Task”
First Deployment Product overview, prerequisites, collector install, and backend connection.
Collector Operations YAML configuration, CLI, service mode, and extension deployment.
Dynatrace Operations Platform setup, app installation, dashboards, and troubleshooting.
Splunk Operations Application installation, dashboard pages, HEC connection, and troubleshooting.

Troubleshooting Quick Access

Section titled “Troubleshooting Quick Access”
Collector Troubleshooting Investigate collection/authentication/export issues on the agent side.
Dynatrace Troubleshooting Resolve ingestion, app, and dashboard issues in Dynatrace.
Splunk Troubleshooting Resolve HEC/index/dashboard issues in Splunk.