-
Notifications
You must be signed in to change notification settings - Fork 105
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
[cygnus-ngsi][OrionStatsSink] Create #304
Comments
Since this is an experimental sink, not required by FIWARE nor the IoT Platform, I'll develop it in parallel to real backlog, using my free time ;) |
Good idea! Orion implements an "/statistics" operation (see https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_Installation_and_Administration_Guide#Statistics) but this OrionStatsSink would be a very useful complement. |
What do you think about feeding Orion? Is it better to update a new "<original_entity_id>_stats" sufixed entity containing the statistics? Or could we take advantage of the metadata and add the statistics to the already existing entity? |
I really love the idea of using attribute metadata for attach statistics to Orion entities. |
Some resources from a previous trial; the following ones can be directly reused:
This can be used as an inspiration of what must be done regarding the sink, but must be adapted to the latests changes in hte core (batches, data_model, etc):
|
What about a sink receiving (certain) Orion notifications and (online) computing some kind of simple statistics for each entity's (numerical) attribute, in order to update new entities at Orion? This could the
OrionStatsSink
:)More details:
Regarding output entities to be updated in Orion, certain naming conventions should be used, e.g. if the entity's name is some_entity_name then the output entity could be named some_entity_name_stats. Other possibility could be to add the statistic values as metadata of the original entity's attribute.
In general, this is an online way of obtaining a subset of all the statistics that the Short-Term historic will be able to generate from previously stored batches.
The text was updated successfully, but these errors were encountered: