Create Incidents Using Rules

Beacons allow you to define rules that StatusCast will follow anytime that beacon receives a ping from a third party source. This allows you to automate actions such as creating and updating incidents from any source through a set of simple conditional statements.

For the purpose of this document we will refer to the following JSON example but it is important to note that your exact data format will be based on the vendor/service that is pinging StatusCast:

815815

sample json

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.
    a. 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).

Example:

We recommend creating an initial valuation. 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.

16001600

sample rule

Once our initial rule/data has been verified and we move on to your THEN section, we can be a little more specific in our rules that would trigger a certain action on your status page. The example below states that in order for StatusCast to create an event the “status” key will need to match the value of TRIGGERED.

15921592

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:

15811581

Title

  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:

16001600

Message template

  1. Choose your AFFECTED COMPONENTS.

  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.

FAQ

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.