Navigation:  Configurable Actions > Operation 'Daten nicht speichern"

If a condition matched and this action is configured, the data won't be saved to the database.
This is useful for filtering - consider the following situation:

A data endpoint is checked every 30 seconds, which is quite frequently and only those datasets should be saved that document errors. This prevents the database from keeping a lot of redundant information if the observed systems work well, but stores everything necessary to track down problems in error situations.

Since the action has no parameters except "Name" and "Description" configuring the action once, in most cases, fully suffices. If you prefer to define it for, e.g. special groups of sensors, don't hesitate to define more than one instance of the operation and give them a meaningful name so as to easily find them again later.

 

Quick Overview: