Any device connected to the Internet could be a sensor on HitHub.
It simply must be able to call a URL.
This means you can create alarm triggers based on events from a HUGE variety of devices
Select a time range your alarms should be check, such as 12:00 to 18:00 or 23:00 to 5:00. Specify which days of the week you want specified alarms to run.
Configure certain alarms to be active and inactive with an alarm profile. For example, you may have a "Home" and "Away" profile for sensors around your house.This allows you and/or other users to quickly activate/deactivate alarms, say when you are leaving your home, or for any other reason.
You may choose which users should be notified when an alarm is triggered. When an alarm is triggered, you may optionally choose to temporarily lock the alarm for a specified time, to prevent it from being triggered multiple times for one exceptional event.
Send events and alerts directly to Google Analytics. You may do this for long-term logging or to combine your HitHub metrics with other metrics. You can define how HitHub values should map to GA event properties.
You can add multiple users to your account and control what permissions each have within your account. As an owner, you will always control much of your account's setup, but you could potentially give certain users the ability to manage sensors, manage alarms, or change the current alarm profile.
Depending on your use case, you can optionally setup sensors so that when a HTTP event request is made, a secret token is required. In such a setup, any event request not containing the token will be rejected. You may require an account level token (shared between all users), or a user specific token, which would basically allow for user authenticated events.