Monitoring Applications and Services

Use these guides to monitor collaboration, SaaS, and business-critical services, including Microsoft 365, Microsoft Teams, Salesforce, Slack, Webex Meetings and Calling, and Zoom. Some articles apply platform concepts like hub-and-spoke agent placement to the application you want to monitor.

Available Guides

• Monitoring Microsoft 365

  • Why use this: Outlines strategies for tracking connectivity to Exchange, SharePoint, and Teams, providing early warning for service degradations.

  • What this is for: Responding to user connection tickets and ensuring comprehensive monitoring coverage.

• Monitoring Microsoft Teams

  • Why use this: Focuses on real-time audio and video performance metrics.

  • What this is for: Applying first-call resolution strategies for call quality complaints and isolating faults.

• Monitoring Salesforce

  • Why use this: Provides best practices for tracking SaaS login and critical transaction flows.

  • What this is for: Tracking vendor SLAs and securing reliable application connectivity.

• Monitoring Slack

  • Why use this: Details hub-and-spoke monitoring architectures and API endpoint tracking techniques.

  • What this is for: Configuring and scaling monitoring coverage across distributed enterprise environments.

• Monitoring Webex Meetings with Endpoint Agents

  • Why use this: Focuses on user session views and local network statistics to pinpoint exactly where meeting traffic is dropping (e.g., VPN vs. Wi-Fi).

  • What this is for: Troubleshooting meeting quality for individual remote users.

• Monitoring Webex Calling

  • Why use this: Discusses VoIP traffic prioritization, DSCP tagging, and QoS metrics.

  • What this is for: Gaining precision in test configuration and tracking voice-quality symptoms.

• Monitoring Webex Meetings with Cloud and Enterprise Agents

  • Why use this: Explains the deployment of external and internal vantage points around Webex infrastructure.

  • What this is for: Managing mass deployment of agents and network topology planning.

• Monitoring Zoom

  • Why use this: Gives best practices for understanding Zoom's distributed architecture and mapping user symptoms to specific network path hops.

  • What this is for: Gathering evidence to quickly isolate issues across distributed architectures.