Difference between revisions of "Developer Introduction"
From Senfi Docs
(Created page with "As a Senfi developer, your primary concern is to get data into Senfi, and to make use of Senfi's rule engine and computed measurement to setup automated alerting and actions....") |
|||
| Line 3: | Line 3: | ||
[[File: Dataflow.PNG|link=]] | [[File: Dataflow.PNG|link=]] | ||
| − | A typical | + | A typical usage follows this pattern: |
# Data is [[Sending_data_to_Senfi|fed to Senfi]] and ingested. | # Data is [[Sending_data_to_Senfi|fed to Senfi]] and ingested. | ||
# Valid data will be saved. | # Valid data will be saved. | ||
Revision as of 17:33, 23 September 2019
As a Senfi developer, your primary concern is to get data into Senfi, and to make use of Senfi's rule engine and computed measurement to setup automated alerting and actions. The following diagram gives you an overview of how data is processed and stored.
A typical usage follows this pattern:
- Data is fed to Senfi and ingested.
- Valid data will be saved.
- Valid data will also be passed to compute measurements that are derived.
- You can make use of live incoming measurement, computed measurement, or historical measurement in your rules.
- You can also configure actions to be taken when a rule is evaluated to be true. Or when a rule goes from true to false.
At any point in time, if the system encounters invalid data or errors, an entry will be recorded. This entries can be examined in the CMS debugger.