Modular Output System Driver
Information
Provides live information being written to the Modular Output System.
Driver Info | Detail |
---|---|
Driver Type: | Live |
Platforms: | All |
Usage
The Modular Output System allows you to take the output of an script or service and make it available through a variety of mechanisms.
One of the things you can choose is to write your data to this driver, delivering live information from alerts, models, analytics or any other service being powered by live information.
Driver Settings
Option | Description |
---|---|
Port Number | The port you would like to receive Modular Output System messages on |
Prometheus URL | When first started, the driver will request all of the current values from this prometheus endpoint |
Output Proxy Options | If not empty, this points to a configuration file for the driver to operate as a modular output system proxy |
Proxy
This driver is both a traditional ARDI driver and is also uses the Modular Output System to be able to distribute any values you write into it.
This is particularly useful if you want to make short-lived data available in a long-lived format.
For example, you might calculate a KPI in a report that you want to record in Prometheus.
The challenge here is that you can't push data to Prometheus. It instead expects you to offer a page of data that it pulls into itself.
However, a report is a single script - it starts, produces its output, and then ends. Since the process is now closed, there's nowhere for Prometheus to read data from.
Here's where the proxy comes in. Since your driver is constantly running, you can use it's Modular Output System features to distribute those KPIs calculated by your short lived reporting process. Your report writes data to this driver, and the driver hosts the Prometheus endpoint you need to record the values.
Point Settings
Option | Description |
---|---|
Key | The name of the Modular Output System point |