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....") |
(Marked this version for translation) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
+ | <translate> | ||
+ | <!--T:1--> | ||
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. | 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. | ||
+ | <!--T:2--> | ||
[[File: Dataflow.PNG|link=]] | [[File: Dataflow.PNG|link=]] | ||
− | A typical | + | <!--T:3--> |
+ | 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 | + | # Valid data* is saved. |
− | # | + | # Data can also be used to calculate [[Computed_measurement|computed measurements]]. |
# You can make use of live incoming measurement, computed measurement, or historical measurement in your [[Rule|rules]]. | # You can make use of live incoming measurement, computed measurement, or historical measurement in your [[Rule|rules]]. | ||
− | # You can also configure [[Rule#Actions|actions]] to be taken when a rule is evaluated to be true. Or when a rule goes from true to false. | + | # You can also configure [[Rule#Actions|actions]] to be taken when a rule is evaluated to be true. Or when a rule output goes from true to false. You can make use of webhooks to integrate with your existing systems. |
+ | </translate> | ||
+ | <div class="important"><translate><!--T:4--> *At any point in time, if the system encounters an unexpected condition or error (eg. due to invalid data), it will generate a log. These log entries can be examined in the [https://ems.senfi.io/cms CMS under debugger].</translate></div> | ||
− | < | + | <span class="right"><translate><!--T:5--> [[Measurement|Next: Measurement]]</translate></span> |
Latest revision as of 14:34, 17 October 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* is saved.
- Data can also be used to calculate computed measurements.
- 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 output goes from true to false. You can make use of webhooks to integrate with your existing systems.
*At any point in time, if the system encounters an unexpected condition or error (eg. due to invalid data), it will generate a log. These log entries can be examined in the CMS under debugger.