influxdata / influxdata/telegraf
OPC-UA Listener plugin support for MonitoringFilter (DataChangeFilter)
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
### Use Case
When subscribing to OPC-UA nodes, and integral part of this subscription model is to assign a [MonitoringFilter](https://reference.opcfoundation.org/Core/Part4/v104/docs/7.17) to the subscriptions.
These filters are used to define the conditions (typically how much a value must change using a [DataChangeFilter](https://reference.opcfoundation.org/Core/Part4/v104/docs/7.17.2)) for when the server should generate a [DataChangeNotification](https://reference.opcfoundation.org/Core/Part4/v104/7.20.2/).
This is essential for managing the subscription data flow in larger industrial systems with thousands of sensors.
Specifically being able to use the DataChangeFilter to specify how much a value must change before subscription data is sent, is critical in systems where analog sensors may generate non-stop high frequency changes without this filter.
### Expected behavior
The client subscription model should expose the MonitoringFilter part of OPC-UA so that filter parameters can be set and modified.
### Actual behavior
MonitorFilter is not yet implemented.
### Additional info
OPC-UA Reference documentation:
https://reference.opcfoundation.org/Core/Part4/v104/docs/7.17
Contributor guide
Assessment
This issue has not been assessed yet.