> For the complete documentation index, see [llms.txt](https://hyperflow.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperflow.sygnal.com/apps/v5.md).

# Hyperflow Monitor

**Most website designers think in terms of a website and web hosting.  The reality is that modern websites are often an amalgam of services, and you have to begin thinking of it as a *****system*****.** 

Many *systems* rely on multiple external pieces such as; 

* Automations ( Zapier, Make, n8n, etc. )
* External API's
* External file stores, such as S3 buckets
* External databases 
* External datafeeds ( RSS, XML, etc. ) 

{% hint style="info" %}
There are a lot of points of failure where things can go wrong and your site will not function correctly. 
{% endhint %}

## Terminology

* **Monitor.** An individual monitor, defined by a URL and alerting rules.
* **Alerting Profile.**  A definition of how to alert you. 

## Monitor Definition

* **Name.**  A name for the monitor, for alerting and reporting.
* **ID.**  The monitor's unique identifier. This is usually an arbitrary UUID that you can create anywhere. 
* **Interval ( mins ).**  The monitoring interval.
* **Expires.**  Timeout when the next alert would occur.
* Message.  
* Event Alert.  Alert handler for events. 
* Expired Alert.  Alert handler for expired alerts.  

## Usage Notes

At Sygnal we often use Hyperflow Monitor for multiple purposes-

For example, let's suppose we have an important purchasing feature on a client site.  Hyperflow Monitor can;

* Alert us every time a transaction is made, with a positive *cha-ching!*  notification 
* Alert us any time a transaction hasn't been seen for specified period of time, so that we can check the system and ensure everything is working