You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current plugin config accepts them (standard Telegraf). In this plugin code the measurement is only given tags from the data acquired from OPC-UA. [opcua.tags] is broken and does not alert
Expected: [opcua.tags]need to be able to add static tags and Telegraf needs to error on incorrect configuration
Schema improvements
The config for a Node in the configuration takes a ’name’ but this is used as the value of the “name” field in the code and the name of the field that contains the value received from OPC-UA in the code.
Current schema: [tag {name="x”}, field{x=<value>}]
Expected:
Default to a field named value with an optional name_override config to change it to something else.
The text was updated successfully, but these errors were encountered:
We ended up adding tags in a slightly different way than this issue proposes because we needed to add tags to a single opc ua node or a group of nodes. You can still use an inputs.opcua.tags section like before, but you can also add tags directly to a node or to a group of nodes.
We also changed the metric schema by removing the name field and allowing each node to change the metric's field name and each group to change the metric name.
Current defects with existing inputs.opcua plugin
Broken Static tag additions
The current plugin config accepts them (standard Telegraf). In this plugin code the measurement is only given tags from the data acquired from OPC-UA.
[opcua.tags]
is broken and does not alert[opcua.tags]
need to be able to add static tags and Telegraf needs to error on incorrect configurationSchema improvements
The config for a Node in the configuration takes a ’name’ but this is used as the value of the “name” field in the code and the name of the field that contains the value received from OPC-UA in the code.
[tag {name="x”}, field{x=<value>}]
Default to a field named
value
with an optionalname_override
config to change it to something else.The text was updated successfully, but these errors were encountered: