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
There are several cases where there are not data about a component in Olex. In these situations data retrieved by data collectors can be overrided. But maintaining a large set of components in this way is not easy. For these reason, a company could decide to set its own "olex" in a MySQL database to avoid reconfiguring each entity data in RISCOSS. In this way, changing this data in the database will result in updates values retrieved by MySQL data collector for each entity.
It would be desiderable to set the number of columns that the SQL query should return and a field to be filled by the user with the SQL query, host, database, user, password... You can see an example of this in the following project:
There are several cases where there are not data about a component in Olex. In these situations data retrieved by data collectors can be overrided. But maintaining a large set of components in this way is not easy. For these reason, a company could decide to set its own "olex" in a MySQL database to avoid reconfiguring each entity data in RISCOSS. In this way, changing this data in the database will result in updates values retrieved by MySQL data collector for each entity.
It would be desiderable to set the number of columns that the SQL query should return and a field to be filled by the user with the SQL query, host, database, user, password... You can see an example of this in the following project:
https://github.com/jpmens/mosquitto-auth-plug/blob/master/README.md
The text was updated successfully, but these errors were encountered: