In Serverless360, you can create alarms from a couple of different places in the user interface:

• In the Overview screen of a Composite Application
• Within a Composite Application, in the section for a component type (for example, queues, topics, Logic Apps, and so on)

Here we will only describe how to create a threshold alarm. As mentioned before, such alarms can be used to monitor whether the components of your solution are in the expected state.

In the previous section, we left off in the Logic Apps section of our ACME Order Processing application, so let's create an alarm from that section:

1. Create an alarm: The blue menu bar on our left-hand side shows Monitor as the last menu option. When we hover our mouse over that menu option, we get the following options:

To create an alarm, we select the Configure Alarms option.

2. Enter the alarm details: After we have selected the Configure Alarms section, a pane shows up where we can enter the details of the alarm. For the following fields, a value can be entered or selected.
3. Alarm name: Enter a descriptive name for the alarm. This field is required and a maximum of 50 characters can be entered.
4. Summary: The notifications sent by this alarm show this summary. This field is not required and a maximum of 100 characters can be entered.
5. Choose alarm type: This dropdown has the following two values:
   • Threshold: Set up an alarm for threshold notifications
   • Health check: Set up an alarm for status checks at defined times
6. Disable alarm for maintenance: By default, an alarm is Enabled, but it might be smart to temporarily Disable the alarm to prevent receiving false notifications.

In our case, we will create a threshold alarm with the following details:

After entering the preceding values, we click the Next button in the lower-right corner of the pane:

1. Enter the Threshold Alert details: As we have decided to create a threshold alarm, the next screen shows fields related to that alarm type. The following fields show up:
   • Notify when violation ends: Configure whether you want to receive a notification once the threshold violation is finished and the alarm is healthy again.
   • If violation persists for: Here you can configure how many minutes after a violation you want to receive a notification. For important components, you want to receive these notifications earlier than for less important components. A value from 1 to 60 minutes can be selected.
2. Number of alerts per violation: This allows you to configure how many notifications you can receive (per violation). This prevents your being bombarded by notifications for the same violation repeatedly, which can lead to you potentially missing more important notifications. A value from 1 to 10 can be selected.
3. Set alerts on set day and time only: By using this option, you can monitor only during the configured day and time. This is helpful, for example, when a component is only available on business days.

In our case, let's stick to the default values and click Next to proceed to the next screen.

4. Configure notification channels: With notification channels, you can configure the means by which you want to receive your notifications. Email is the default notification channel, but you can configure multiple others, such as pager duty, Slack, webhook, OMS, and Microsoft Teams. These notification channels can be configured under Settings | Notification Channels. As none of the aforementioned notification channels have been set up so far, we can only configure the email notification channel. Hence, in this pane, only the following fields show up:
   • Serverless360 email channel: Set whether you want to use the email notification channel.
   • Recipient email address: Email address to which the notifications will be sent. Multiple addresses can be entered, separated by a comma or a semi-colon.

In this case, we'll use following values:

5. Save the alarm: Now we have configured all the monitoring rules, the only thing left is to save the alarm. Click the blue Save button in the lower-left corner of the pane. Once the alarm is saved, the overview screen containing all the alarms for the ACME Order Processing application will show up:

We've now created an alarm, including monitoring rules. With this, we have configured how we will monitor; next, we'll configure what we want to monitor.