Difference between revisions of "V2/Concepts/Data Feeding"
From Senfi Docs
| Line 13: | Line 13: | ||
<div class="important">*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://app.senfi.io/cms CMS under debugger].</div> | <div class="important">*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://app.senfi.io/cms CMS under debugger].</div> | ||
| + | |||
| + | ==== What's Next ==== | ||
| + | ----- | ||
| + | * [[V2/Concepts/Intro to Measurement|What is a Measurement]] | ||
Revision as of 01:55, 25 June 2021
How are data fed into Senf
The following diagram gives you an overview of how data is processed and stored into Senfi after it is received from Connectors, and how Senfi's rule engine and computed measurement is used to setup automated alerting and actions.
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.