Uptime Monitoring Beacon

Uptime Monitoring and Application Performance Service Beacons

If you created a beacon using a known provider a default rule set will be imported for you, but can be modified afterwards if need be.

Creating a Monitoring Beacon with a Webhook

Go to Beacons and Select Uptime Monitoring or Application Performance Beacon. Follow the dialog to create a beacon for your service, or if not shown in the menu, pick generic webhook or generic email address creation.


General Beacon Information

In this section you can update the following:

Name Name of the beacon
Description Brief description of what the beacon does
Escalation Policy Allows you to associate a Beacon Escalation policy
Process Beacon As Who created or is in charge of the beacon
Webhook Url URL used to trigger the beacon


Here you can setup the rules that will govern the beacon. Here you will set the rule (or rules) to see if any actions need to be taken. This is the global rule (or rules) for the beacon and it will be evaluated first.

To add a rule click on the plus sign to the right of the Rules section.


A rule consists of an IF/THEN statement, that will tell StatusCast what to do when the If statement is met.


To setup the IF portion of the statement please click the the Add Rule button under the IF. Then the area to setup the condition will show. Here is were the elements that are going to be evaluated are specified. To add a condition (AND, OR) or remove one that has been added click on the hamburger button to the right of the condition area.


After you have set the IF portion, you have to choose what is done when the condition is met. This is done by checking the box in front of the wanted action found under THEN; you can check as many or as few actions as needed.



Here is a description of each action:

SET STATUSYou can set a status (UP or DOWN) for the beacon itself.
ASSIGN TO TEAMThe beacon can be assigned to a predefined team in the application.
ASSIGN TO USERThe beacon can be assigned to a user in the application.
EXTRACT COMPONENTSUse this action to correlate what component(s) in StatusCast are affected by this beacon, specifically which object in your JSON is correlated to component names or component external IDs.
CREATE INCIDENTSetup what will show in the incident.
UPDATE INCIDENTSetup what will show in the update to the incident.
SUBSCRIBER NOTIFICATION CHANNELSSelect the notification channels to be used when creating an incident and notifying subscribers.
UPDATE COMPONENT STATUSSet the status (Available, Unavailable, Maintenance or Degraded Performance) of a particular component.

Note: Under each action you may find one or more options that need to be set to complete the action setup.

If you already have a predefined rule set, you have the option to import it in the General section of the Beacon at the top.


Exporting Rule Sets

Also, if you are going to use the same rule set in another beacon setup, you have the option to export it in the Rules section.


Once you have everything you need set up, please remember to click the UPDATE button at top.

Most Common Beacons

In general, beacons are setup to evaluate information in a ping from a service to see if a service is up or down and then execute any action or actions. To do this the beacon should grab the necessary information to see if the conditions are met. If the service is down, create an incident. If the service is up, create an update.

To be able to do the above, the beacon should have the following:

Global IF - main condition to be evaluated.


Targeting Keys/Value Pairs

How to target keys/value pair in my Json file

In order to target any keys you will first need to start with “$.”, then proceed with the name of the key. Use dot notation if the target is embedded in other objects.

General workflow for creating a conditional rule

  1. Pick an IDENTIFIER to begin your rule. Recommended Identifier: Content - Value of a key/value pair in a Json file.

  2. Select a key from your Json file to check against the criteria operator.

  3. Pick a CRITERIA OPERATOR to validate against your key from your json file.

  4. Enter the value of the respective key you selected in step 2. NOTE: Not every criteria operator will require this step (i.e. Any).


We recommend creating an initial evaluation. For example, the rule below states that if our “status” key in our json payload contains any value, please proceed to the THEN tasks/rulesets. This simple check will eliminate any empty/false data that is passed down to your status page and eliminates the risk of creating an incident inappropriately.


sample rule


Get information to evaluate additional conditions.



If a service is down, you can use rules to create an incident.

1001 998

The example below states that in order for StatusCast to create an event the “status” key will need to match the value of TRIGGERED.


sample incident creation rule

Defining your incident

Rules and incidents can be quite intricate due to the high level of customization. Here is a simple and recommended set up for your incidents.

  1. [Optional] Wait (minutes) - Define a time in minutes to delay the post of your incident.

  2. Define a TITLE for your incident
    a. You can use data from your Json file. Please see the example below:



  1. Select an INCIDENT TYPE from the following:

a. Performance
b. Scheduled maintenance
c. Service unavailable
d. Informational

  1. Create a new MESSAGE or choose from a TEMPLATE.

You can use data from your Json file. Please see the example below:


Message template


  2. Select to AUTO PUBLISH your incident or create a draft.

  3. Define if the incident will COUNT TOWARDS DOWNTIME.

Defining updates

You can create rules for updates on open incidents too. You have two options when choosing an incident: Informational or closed.

  1. Choose the STATUS of your components. Keep the same status as the original incident or change it to something else.

  2. Choose the TYPE of update.
    a. INFORMATIONAL: Provide updates to an ongoing incident. Incident will remain open.
    b. CLOSED: The resolution post to an open/ongoing incident. Incident will be closed once published.

  3. Create a MESSAGE or select one of your templates.


Can I create a thread or stack of rules for a specific action?

Beacon conditions will allow you to create subsequent rules that can be stacked on each other. Use the HAMBURGER ICON on the right side of the rule to add additional conditions. Available options to choose from this dropdown include AND, OR, & REMOVE.

  1. AND: All conditions must be met in order for the action/task to be performed.
  2. OR: One of the conditions must be true/valid for an action/task to be performed.
  3. REMOVE: Removes the current rule.


If a service is back up you can update or resolve your incident