To configure what we want to monitor, we must map the artifacts we want to monitor to an alarm. After that, we can configure the actual monitoring:

1. Add artifacts from the Composite Application to the alarm: In this step, we will map some artifacts to an alarm. To do so, we must navigate to the Monitoring Dashboard. From the left-hand side menu, under Monitor, we select Monitoring Dashboard:

The Monitoring Dashboard still looks a bit empty, so let's start by adding some Logic Apps to it by clicking Add Entities. From the menu that appears, select Logic Apps, after which a pane shows the Logic Apps that we added earlier to the Composite Application:

Select both Logic Apps and click Save. We are redirected to the monitoring dashboard, which now shows both Logic Apps:

Although both Logic Apps are now added to the alarm, we still need to configure what we want to monitor for. So, that's the next step we will concentrate on.

2. Configure monitoring: For all the artifacts we add to an alarm, we can configure what exactly we want to monitor. As, in our scenario, we will be monitoring a few Logic Apps, we can monitor the state of these Logic Apps. Logic Apps can have the following states, which can also be used for monitoring:

• • Enabled (default)
  • Disabled
  • Deleted
  • Completed
  • Suspended
  • Not specified

Configuring which state to monitor for can be done by clicking on a Logic App, after which the Configure Properties screen appears. From the following screen, you set up the monitoring of Logic Apps in three steps:

1. Enable monitoring: The first step is to enable monitoring for the Logic App. We achieve this by flipping the Enable Monitoring switch. After that, the Edit button will be enabled.
2. Click Edit: Next, we click the Edit button to be able to configure the state for which we want to monitor. The Edit button becomes replaced by Save and Cancel buttons.
3. Configure the expected state: From the EXPECTED STATE dropdown, we configure the state we want to monitor. In most cases, we want a Logic App to be Enabled, but there might be very good reasons to have your Logic Apps in a different state.

After we have selected the EXPECTED STATE (Enabled), we click the Save button.

This wraps up setting up a threshold alarm for this chapter. If our Logic App is not in the enabled state, we receive a notification in our email inbox. The alarm we created only contains a Logic App, but the alarm can easily be extended with monitors for other component types supported by Serverless360. If you prefer not to use email, you could use another notification channel that Serverless360 supports.