ManualTrigger Automate

Automate alerts for network latency and loss on Meraki with the ManualTrigger Automate workflow. This solution runs every 5 minutes during business hours, monitoring network performance and sending notifications to Microsoft Teams for any issues exceeding 300ms latency or 2% loss. It efficiently logs alerts in Redis to prevent duplicate notifications, ensuring timely responses to network problems.

7/8/2025
23 nodes
Complex
schedulecomplexschedule triggerredismicrosoftteamssticky noteautomationadvancedapiintegrationcron
Categories:
Schedule TriggeredComplex WorkflowData Processing & Analysis
Integrations:
Schedule TriggerRedisMicrosoftTeamsSticky Note

Target Audience

This workflow is ideal for network administrators and IT professionals who manage Cisco Meraki networks. Specifically, it is beneficial for those who need to monitor network performance, identify issues related to latency and packet loss, and ensure timely notifications to technical teams for prompt resolution.

Problem Solved

This workflow addresses the challenge of monitoring network performance by automatically checking for high latency and packet loss across multiple Cisco Meraki networks. It ensures that alerts are sent to the appropriate teams in Microsoft Teams only when issues arise, preventing redundant notifications for already acknowledged problems.

Workflow Steps

  • Schedule Trigger: The workflow runs every 5 minutes from 8 AM to 5 PM on weekdays.
    2. Get Meraki Organizations: Fetches all organizations associated with the Meraki account using an API call.
    3. Get Network IDs: Retrieves network IDs for each organization to monitor their performance.
    4. Get Uplink Loss and Latency: For each network, it collects uplink statistics including latency and packet loss over the last 5 minutes.
    5. Combine Data: Merges the uplink statistics with network information to create a comprehensive dataset.
    6. Calculate Averages: Computes the average latency and packet loss for the last 5 data points.
    7. Filter Problematic Sites: Identifies networks that exceed the thresholds of 300 ms latency or 2% packet loss.
    8. Check if Alert Exists: Verifies if an alert for the identified network is already logged in Redis to avoid duplicate notifications.
    9. Send Alerts: If no alert exists, sends a notification to the technical team via Microsoft Teams, including details such as network name, average loss, and latency.
    10. Log the Alert: Records the alert in Redis with a 3-hour TTL to ensure timely follow-ups on unresolved issues.

    • Customization Guide

    Users can customize this workflow by:
    - Adjusting the schedule in the Schedule Trigger node to fit their monitoring needs.
    - Modifying the threshold values for latency and packet loss in the filtering node to suit specific operational requirements.
    - Updating the Microsoft Teams chat ID in the Message Techs node to direct alerts to the appropriate channel.
    - Adding additional nodes to include more metrics or integrate with other systems based on organizational needs.