weeks away from running out of space. Then there are the most important notifications
– security alerts that can prevent, or at least limit, the damage from a hack or security
breach. Your cloud profile will dictate how you handle each type of alert.
SaaS, PaaS and IaaS
Cloud-based SaaS offerings, which are used for business purposes like scheduling travel
or managing HR applications, require the least amount of alerting. Customers do not
control any of the data, runtime, middleware, operating system, virtualization, storage or
networking connected to these applications; they just consume the services. So, all the
cloud-native default alerting features for the applications should suffice. What custom-
ers focus on will depend on what the organization is looking for. Figure 1 shows a sam-
ple of Azure SaaS alerts.
Figure 1: Sample SaaS alerts
In the example above, alerts can be configured simply by setting some default policies.
What remains challenging is deciding which policies are important. Normally, this is done
in a specific three-step process:
1. Determine what policies in your data center map to the SaaS model
2. Decide if you need to modify or change any of these policies?
3. Validate and document the new policies
Figure 2 shows a sample of alerting in a PaaS environment.
38 | THE DOPPLER |
FALL 2019