How Pulse works?

A pulse is a heartbeat monitoring handler. It has a unique URL to which you send HTTP requests. It receieves these requests and validates if you set custom rules for the parameters to be dispatched to your pulse. You can use pulse to monitor different services and devices like the following.

🖧 cron jobs

🖥️ servers

🌡️🚚📷 smart devices

Expected response

A pulse expect at least one response within the period you set. Let's assume, you have a pulse that is waiting for a request to arrive every 30 minutes. When pulse receives a request, it waits for another request to arrive in the next 30 minutes. At the end of this 30 minutes, a notification is sent to you if a request is not received yet.

Example HTTP request:

https://pulse.webgazer.io/2-0e6217056425

In addition to periodic requests, pulse also validates the paremeters which you send within the HTTP request. If the parameter value does not meet your criteria that you previously set, a notification is sent to you.

Example HTTP request:

https://pulse.webgazer.io/2-0e6217056425?success=true&time=15

Parameter types and relation expressions

A pulse accepts two types of parameters.

  • integer
  • string

You can post parameters in these forms to validate with rules. Rules are set when setting up a pulse and could include one of a combination of the following relation expressions.

  • == for equal to
  • ≠ for not equal to
  • < for less than
  • ≤ for less than or equal to
  • > for greater than
  • ≥ for greater than or equal to
For strings, only equal or not equal type expressions are allowed.

💡 Learn more about parameter validation and use of relation expressions on Parameter validation.

Incident tolerance

You can set a tolerance for the request period. This aims to aviod creating incidents for request arriving late due to normal circumstances of your job. If you set a 5 minutes latency for an hourly pulse, the next request is expected to arrive no later than 1 hour and 5 minutes from the time last one arrived. If the request is not received in this period, an incident is registered.

Alerts

In case of an incident, WebGazer sends a notification to your preferred channel. You can set an instant alert (or delayed) for a pulse under the Alerts section.

💡 Learn more on Alerts.