Observations: Filter & Process Events

Observations describe how to sample/store resource data and what should be done when the data meets a specified condition. An Observation then generates an event containing that data when the rules defined by the Observation are met. This event is then routed to different destinations (e.g., to another resource, to the cloud, etc.).

When defining an Observation, you can optionally configure how to manage, manipulate, and filter data that has been observed from a resource, which in turn, defines how and when an event is generated. The following topics describe these configurations:

• Buffering Data: buffer data that is arriving at some frequency from a sensor or inputs.
• Filtering Emitted Events by Rules: define a threshold (e.g., minimum value) that the observed values must satisfy before an event can be generated.
• Applying Functions to Observation Buffers: perform a calculation on buffered data (e.g., calculate the average value) before generating an event.
• Throttling: define the rate at which to generate an event. This can be useful when input is being received at a high frequency, but you don't want to generate an event for every value.