Custom Event Sources

There are times where you need more flexibility when sending an alert to an on-call team member. In some cases, you may need to include different details in the message, or change the alert level or notification priority. In those advanced use-cases, FireHydrant is equipped with the ability to define your own function to parse Signals the way you want them. You can think of these as lambdas that are run for each incoming event into your FireHydrant account, and emit an Event type.

How it works

When FireHydrant receives incoming payloads for the default list of sources we support, we convert them into a common data structure we call an Event. The order looks like this:

1. HTTP POST https://signals.firehydrant.com/v1/process/{orgkey}
2. Parse incoming payload
3. Transpose it into an Event object
4. Store the Event, and fire any alerts that are relevant for it

For step 3, we have a common list of what we call “transposers” – these are the ones you find on the main page of event sources in FireHydrant. They work for most use cases you may have.

But when these pre-built transposers don’t suit your needs, you need a bit more horsepower. This is why we chose JavaScript to parse payloads that result, ultimately, into the Event data type. The flow changes to be:

1. HTTP POST https://signals.firehydrant.com/v1/relay/custom-source/{orgkey}
2. Load custom JavaScript expression (based on custom-source in the URL)
3. Evaluate and execute the function with the incoming JSON payload
4. Take the result of the transpose function we ran
5. Validate the transpose function returned a valid Event
6. Store the Signal, and fire any alerts that are relevant for it

Limitations

• As much as we’d love to give people as much time as they need to process signals, we do require that these scripts evaluate in under 50 milliseconds. Trust us, we don’t dilly dally on these.
• Scripts do not have access to any IO calls (filesystem, network)
• Scripts must be compatible with ECMAScript 5.1

Getting started

You can write your own transposer script to ensure that FireHydrant understands the payload. Create your own custom event source on Signals > Event Sources > Add custom event source.

Transposer function

A valid JavaScript transposer script must:

1. Have the function name transpose.
2. Takes in 1 input as a parameter.
3. Returns a valid Event Data Model object.

Custom event sources are not limited only to the transpose function, either. You may define any valid Javascript function or expression and use them. For example, you may have a function to determine the Signal level that should be used.

const levelMap = {
  "critical": 2,
  "error": 1,
  "warning": 1,
  "info": 0,
  "debug": 0
}

function payloadLevel(payload) {
  if (!payload?.level) return 0;
  return levelMap[payload.level.toLowerCase()] || 0;
}

Provided input structure

Transpose function takes in input argument, which consist of request payload and body in the following structure:

{
  headers: {
    "Content-Type": "application/json"
  },
  data: {
    // The request JSON payload here
  }
}

Debugging

It’s very likely that, at some point, you’ll need to debug what’s going on with your custom script. In lieu of a console.log function, we provide a debug function that will automatically display the provided argument in the FireHydrant.

The debug function is a variadic function as well. Meaning you can pass multiple arguments to it.There is a hard limit of 10 debug calls per execution of your script.

📘

Note:

There is a hard limit of 10 debug calls per execution of your script.