-
Notifications
You must be signed in to change notification settings - Fork 29
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
Cant create type in Grafana #22
Comments
It seems that the Grafana OpenTwins App may not have been configured correctly. Ensure that you have entered the correct addresses for both the Ditto NGNIX instance and the Ditto Extended API instance. Additionally, check your browser's console for any error messages that could help identify the problem. |
Hello. I have same problem but creating a type page has the button but not in the policies' page where nothing is showing. The error in the console is : accessing that url on browser gives a void message : I'm deploying using Minikube. Grafana, the extended API, the Ditto NGINX and Mosquitto are accessible from Internet as I'm deploying on cloud with openstack instance with a floating IP. Grafana OpenTwin plugin is well connected to the Ip addresses of both Ditto NGINX and Extended API. Running API queries such as IP_Ditto_NGINX/api/2/whoami works, inserting and finding a new policy through curl to IP_Ditto_NGINX/api/2/policies/id_policy works. However, in the installation files, it is expected that I find default:basic_policy if I query Ditto NGINX, but it seems it is not their ""error": "policies:policy.notfound",". I was thinking it could be a problem with mongodb not connected, but as long as I insert and I can find a test policy then it is connected. What could make policies not loading ? Thank you. |
@xxabdelxx you can try using the Eclipse Ditto API endpoint Here is an example of the policy :
|
Hello, i tried to deploy opentwins, configured it, but then when i tried create type there was no button to create a type
The text was updated successfully, but these errors were encountered: