-
Notifications
You must be signed in to change notification settings - Fork 10
Plugin Health Check Failed #54
Comments
This was what I got from the build when I did the make build command. Is there any other way to test and make sure that the file is builtcorrectly?
|
I downloaded the opcua-datasource-main github file and built that, then used it for the data_dir configuration of plugin.grafana-opcua-datasource. For clarity's sake i wanted to know if this was the correct file to build and reference. |
Currently I decided to walk myself back through the process and ran into an issue with the yarn dev | yarn build step.
So far thats the only issue I've had. Using the make build command does work, but I think this might've been the reason as to why my plugin health check failed. |
Hey @KeithSprings51 would you mind providing a quick summary of any issues? Looks like it's just build issues? |
Version Platform What steps will reproduce the bug? To solve this issue I used several commands in yarnpkg/yarn#6663. Yarn add puppeteer --ignore-scripts After following these steps I was able to successfuly do a yarn install: After that I attempted to do the yarn dev | yarn build command, and came up with the result:
Should I upload the currently built file I have right now? How often does it reproduce? Is there a required condition? What is the expected behavior? Additional Information: Additional Questions: |
An update on the issue, I decided to do this on windows without the virtual machine running. I wasn't able to do a proper yarn install so I used npm instead. Once I finished the directions and made my file I tested my datasource and it still gives me the same error. |
I switched the logging to debug mode and might've found what was causing the problem
The issue is that I'm not too sure on how I could possibly fix this. From my understanding the only way I can enable settings in grafana is to do it through the defaults.ini file, but most of these aren't found in defaults.ini. Is there another way that I can enable the unsupported value types? |
Hey @KeithSprings51, I could take 15 minutes and get on a screen share with you if that would help. |
Hi @srclosson I just saw this message, I don't have a proper microphone to communicate to you with but I'd be willing to screenshare too.
For context, right now I'm trying to connect the PLCNext to this OPCUA grafana datasource. My settings inside the configuration file are this.
And these are the settings to my grafana opcua datasource. |
You shouldn't have to worry about this config:
That's managed by the plugin config editor. Perhaps it would be helpful to just get an update as to what problems you have that remain? What platform are you running the plugin on? |
I'll make sure to remove them from the config. The platform I'm currently running the plugin on is windows 10. The datasource I'm using is PLCNext, and its pulling data from an axcf2152. |
To keep you up to date on the issues I'm having right now I believe something is wrong with the IP address. I do know that our PLC's IP address is 192.168.0.7, but when I try to connect to it with the proper authentication it returns an error saying the "Endpoint does not support the user identity type provided." I did some searching and found on this site https://www.inventcom.net/support/opc-standard/opc-ua-client that the problem would be my username and password. I'm using the same username and password for when I use UAexpert so I can't see how that could be the problem. |
The OPCUA Datasource is now deprecated, and as a result, we are closing all open issues in this repository. This deprecation means that this plugin won't receive any feature updates or bug fixes except critical security fixes. Thank you for your understanding. |
After using the make command for the file for grafana the plugin check still fails.
I've done every step in the installation tutorial, and the grafana plugin file location for data_dir should be correct.
What else should I add to make troubleshooting easier?
I did use yarn test during the building process, but that was because just doing yarn build after the installation didn't work.
The text was updated successfully, but these errors were encountered: