Don't blink, this is gonna be a very quick overview of Hrbr.
If you really don't like reading documentation and just want to understand the gist of what's going on, you have come to the right place.
To begin, we assume you're familiar with HTTP APIs, JSON, and a few other things.
Hrbr receives Beacon Messages from whatever you're monitoring in the form of a valid JSON object. That JSON is totally up to you. Beacon Messages are POSTed through a Hrbr API endpoint (creatively named /beacon). Messages are regular POSTs with a few header entries for security and identification. You can easily POST a Beacon Message using curl.
It's that simple.
Once a Beacon Message is received, it's stored in private database collection, and simultaneously emitted to any listening elements interested in the Beacon stream.
Hrbr provides built-in listeners called Foghorns and Tugs that can perform actions based on the information in the Beacon stream. Typical actions are raising a Slack/SMS/Email alert, emitting feedback Beacon Messages, or firing a webhooks. You can also create your own Foghorns that can run anywhere you can get a WSS connection. And soon, we will provide a mechanism for you to write your own Foghorns and Tugs that run within Hrbr.
Beacons are akin to agents in other monitoring solutions. They are often pre-written solutions (check our catalog) for specific use cases like logging, monitoring mobile apps (iOS, Android) or instrumenting a web server. All Hrbr Beacons are open source.
And now you're probably wondering about the database full of messages. Those messages are retained for a programmable period of time, then tossed. These historical messages are used for creating Views through the Hrbr Web App, and there are historical query endpoints in the API as well.