The Service Properties Module documentation mentions:
"By default, ME will alert on SQL services where the start mode is Auto, and status is not “Running” or “Unknown”. This means that any SQL service with a start mode of Manual or Disabled will not show up in the default alert. Likewise, services which are not SQL services are not alerted on automatically. You can of course change this behavior (by changing the Alert.ServiceStatus stored procedure call in the job)"
Here, we'll show you how to alert on a non-SQL service. In our example, we'll set up a new job to alert on SkypeUpdate services that have startup type=Auto on all Gold servers.
 

1. Duplicate the AlertServiceStatus% Job

First we'll create a new job based on the existing SQL Server service alert job.
  1. Script out the AlertServiceStatus-GOLD job.
  2. Search and replace to change "AlertServiceStatus" to "AlertServiceStatus-Skype".
  3. In the sp_add_job statement, set @enabled=0 to temporarily disable the job.
  4. Run the script.
 

2. Edit the job step

Open the job from Object Explorer, then open the exist job step. The step will likely look very much like this: 
EXEC [Alert].[ServiceStatus] @EmailProfile='ServiceStatusProfile' ,
     @ServiceLevel='Gold', 
     @ServiceName = '%SQL%',
     @StartMode = 'Auto',
     @IncludeDefer = 1,
     @IncludeException = 1;

Change the value for @ServiceName to 'SkypeUpdate', and click OK to save the step command.

(You can, of course, modify the schedule as appropriate.)
 

3. Enable the job


Enable the job, and you're all set! You'll start getting alerts for downed SkypeUpdate services, along with the standard Defer and Exception code, if any of those "Auto" services are down.

See also: Service Down Alerts