Rivery is an ETL as a service tool which enables you to easily collect and manipulate data before sending it to your destination of choice. Anodot has several integrations with Rivery:
- Rivery ETL Channel - Enables you to send Anodot alerts to Rivery. Those alerts can then be stored in a database of your choice for further processing. See details below.
- Rivery as a data source - Enables you to leverage Rivery to collect information from various data sources, standardize them and stream them to Anodot for monitoring, alerting and remediation. See details here.
Creating an ETL channel out of Anodot based on Rivery can be done in two modes - 'push' and 'pull'.
Push Mode
The 'push' mode enables you to send Anodot alert triggers you recieve to a predefined 'river' and then store the results of that trigger in your database of choice (currently support - Google BigQuery and Snowflake). You can find a template for that river as a Rivery Kit here. From an Anodot perspective, this channel is a regular 'webhook' channel. See here about how to define such a channel here.
The advantages of this mode is that it enables you real time update of the triggers - every alert trigger will immediately be written to your database, similar to how other channels behave.
Pull Mode
The 'pull' mode enabled you to periodically poll Anodot using the Anodot API to get data from Anodot into your database. This mode is suitable mostly for use cases where you want to extract the data from Anodot. We will publish a document explaining how to build such a River in the upcoming days.
