Troubleshooting Notifications

This topic covers troubleshooting techniques for Notifications.

Message not received

Tip

Assess alarms and messages using their unique identifiers. See Prevent Processing of Duplicate Items. To view the format used by alarm messages, see Message format and examples.

Check these items: 

  • Alarm firing transition: If the message is a result of a firing alarm, then view the history of the alarm. Note times for any transition to a firing state. You'll use noted times for comparison to metrics for your topic ("Publication and delivery").

    To view history for your alarm
  • Publication and delivery: Note times for messages published to your topic as well as messages delivered to your topic. Compare to times of the firing alarm or other inciting incident.

    To view timing of published and delivered messages for your topic

Function not invoked or run

This section provides troubleshooting information for function subscriptions. For an example function subscription, see Scenario A: Automatically Resize VMs.

Note

The Notifications service has no information about a function after it's invoked.

Tip

Assess alarms and messages using their unique identifiers. See Prevent Processing of Duplicate Items. To view the format used by alarm messages, see Message format and examples.

Check these items: 

  • Message receipt: See Message not received.
  • Function invocation: Note times for invocations of your function. Compare to times of the firing alarm or other inciting incident.

    Note

    If this is the first invocation, response may be delayed.

    To view timing of invocations for your function
  • Function run: Note times for runs of your function. Compare to times of the firing alarm or other inciting incident.

    To view timing of runs of your function (metrics)