Ingest event from Meraki controller

From version 12.8.330, OpManager supports ingesting events directly from Meraki API controllers. This help document outlines the prerequisites, limitations, and steps for configuration.

Table of Contents

• Limitations
• Pre-requisites
  • Webhook Template
    • Liquid Headers
    • Liquid Body

Limitations

• The OpManager server should be accessible from outside the network as well, since the Meraki controller is cloud-based. (NAT configuration should be done.)
• Meraki has a constraint that it can send webhooks only via the HTTPS protocol.
• The receiving web server must have a valid SSL/TLS certificate signed by a globally trusted Certificate Authority (CA). Learn more.

Pre-requisites

Webhook Template

Servlet: /events/webhook

A new webhook template must be created with the following parameters:

Liquid Headers

Liquid Body

Mandatory Params:

• alarmCode: Unique identifier for the alarm
• serialNumber: Serial number of the device
• severity: Level of the alarm severity
• eventType: Type of the event
• message: Description or details of the alarm/event

Optional Param:

• Entity (Should be made sure that the entity remains same for Up and Down Events)

Sample Webhook Template Configuration:

    {
        "alarmCode":"{{alertTypeId}}",
        "serialNumber":"{{deviceSerial}}",
        "severity":"{{alertLevel}}",
        "eventType":"{{alertTypeId}}",
        "message":"{{alertData | json_markdown}}"
    }