the_information_nexus/work/tbx/test.md

Meraki Webhooks in the MNE Device Failure Incident Management Process

Meraki webhooks can be used to automate the MNE device failure incident management process in several ways:

• Generate a Remedy trouble ticket automatically when a Meraki device failure occurs.
• Notify ETS or another IT team of a Meraki device failure via email or Slack.
• Escalate a Meraki device failure to the MSO team (Tier II) automatically if ETS cannot resolve the problem.
• Notify the customer of a Meraki device failure automatically via email or SMS.

To use Meraki webhooks to automate your incident management process, you will need to:

1. Create a Meraki webhook subscription for each event you want to monitor.
2. Specify the URL of the service that you want to receive the webhooks in the webhook subscription.
3. Configure the service to take the desired action when it receives a webhook notification.

Example:

To generate a Remedy trouble ticket automatically when a Meraki device failure occurs, you would:

1. Create a Meraki webhook subscription for the alert/device/down event.
2. Specify the URL of the Remedy API in the webhook subscription.
3. Configure the Remedy API to generate a trouble ticket when it receives a webhook notification.

Once you have configured the Meraki webhooks, you can test them to ensure they work correctly. Once you are satisfied that the webhooks are working properly, you can enable them in production.

Benefits of using Meraki webhooks to automate your incident management process:

• Improved efficiency
• Reduced workload
• Improved communication

Overall, Meraki webhooks can be a valuable tool for automating the MNE device failure incident management process and improving your response's efficiency, effectiveness, and communication.

Device Has Stopped Responding to Polls:

• alert/device/down
• alert/device/unresponsive

Device Has Lost Power:

• alert/power/fail
• alert/power/offline

Chassis Down:

• alert/chassis/down
• alert/chassis/offline

Unresolved Fault Detected:

• alert/fault/unresolved
• alert/health/failed

Here's an example of a fault alert message:

{
  "event": "alert/device/temperature/critical",
  "sn": "ABCD12345678",
  "name": "Switch Name",
  "timestamp": 1663612800,
  "temperature": 100
}