Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "SensiNact/Bridge-sensinact-storage"
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | [[Category:sensiNact]] | ||
+ | |||
== Description == | == Description == | ||
Line 6: | Line 8: | ||
* bridge ''storage-agent'' activated (using <code>sensinact -c</code>) | * bridge ''storage-agent'' activated (using <code>sensinact -c</code>) | ||
− | * An instance of [[ | + | * An instance of [[SensiNact/Historical-storage|Sensinact Storage Service]] available |
== How to use it == | == How to use it == |
Latest revision as of 11:16, 23 February 2024
Description
This bridge allows sensinact to persist all the changes performed in a sensinace resource into a Sensinact Storage Service, keeping the historical evolution of the resource.
Requirements
- bridge storage-agent activated (using
sensinact -c
) - An instance of Sensinact Storage Service available
How to use it
In order to store the infomation progress in the platform, it is necessary to indicate the storage address, a login and password for that service.
To specify those informations you have to edit the file cfgs/storage-agent.properties located in your sensinact compilation. In this file you can add the information:
# Storage Agent broker=http://yourbrokeraddress/write/measure login=admin password=admin