-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inputs.opcua missing support for arrays #8475
Comments
This can be potentially achieved using a combination of processors and aggregators, but the configuration for an array becomes very long and not practical. Adding the possibility to handle this automatically would be better. Thanks |
Thanks for the issue and info @mirkocomparetti-synesis. I'm going to link this to #8083 and close this issue so we don't have duplicates open. Feel free to add any information to that issue. |
I also would very much appreciate this feature! In the meantime I wrote a quick and dirty workaround that stores the array as a string in influx
|
Hi! I am trying to import arrays and am wondering if there is a solution available that I have not stumpled across so far. I have not been successfull in importing arrays as of now. If you have any advice that can help me I would be delighted! |
Hello @nicolasj92 , could you explain how you have implemented the function? Inside telegraf? @mirkocomparetti-synesis , do you have an idea about the processors and aggregators that I should use? |
Relevant telegraf.conf:
System info:
Ubuntu 20.04, Telegraf 1.16.2 (git: release-1.16 962082f), InfluxDB v1.8.3 (git: 1.8 563e6c3d1a7a2790763c6289501095dbec19244e)
Steps to reproduce:
Expected behavior:
Arrays should be imported as separated fields, just like it happens in mqtt consumer when an array is fed to the plugin in json format.
Actual behavior:
Array values are not imported, as shown in picture
Additional info:
As an example, this json
is correctly translated into multiple fields by the mqtt consumer with this configuration
see picture below
Thanks!
The text was updated successfully, but these errors were encountered: