Meraki packet loss and latency alerts to Microsoft Teams

by Gavin · 5,448 views · created 2024-01-17 · DevOps

What this workflow does

This workflow has 16 nodes and runs on a schedule (cron */5 8-16 * * 1-5) (plus 1 other trigger). Along the way it connects Redis and Microsoft Teams. It also calls api.meraki.com over HTTP.

How it runs

Trigger: On a schedule (cron */5 8-16 * * 1-5) (plus 1 other trigger).

1. Get Meraki Organizations (HTTP Request): calls api.meraki.com
2. Get Org Name & ID (Edit Fields (Set)): sets or maps fields
3. Get Uplink Loss and Latency (HTTP Request): calls an HTTP API
4. Get Network IDs (HTTP Request): calls an HTTP API
5. Combine latency to its respective Network (Merge): merges the data from its input branches
6. Sets Network Variables (Edit Fields (Set)): sets or maps fields
7. Makes Latency and Loss Filterable (Edit Fields (Set)): sets or maps fields
8. Average Latency & Loss over 5m (Code): runs custom JavaScript code
9. Filters Problematic sites (Code): runs custom JavaScript code
10. Check if Alert Exists (Redis): get

…plus 4 more steps. See the full node list below.

Services it uses

RedisMicrosoft Teams

HTTP calls to: api.meraki.com

Before you upgrade to n8n 3.0

Nodes used (8)

• Manual Triggern8n-nodes-base.manualTrigger
• HTTP Requestn8n-nodes-base.httpRequest
• Edit Fields (Set)n8n-nodes-base.set
• Mergen8n-nodes-base.merge
• Coden8n-nodes-base.code
• Schedule Triggern8n-nodes-base.scheduleTrigger
• Redisn8n-nodes-base.redis
• Microsoft Teamsn8n-nodes-base.microsoftTeams

From the author

This Template gives the ability to monitor all uplinks for your Meraki Dashboard and then alert your team in a method you prefer. This example is a Teams notification to our Dispatch Channel Setup will probably take around 30 minutes to 1h provided with the…

View the original on n8n.io → Check your own copy