3,072
edits
Metropolis Microservices/RidgeRun Services/Engagement Analytics: Difference between revisions
Metropolis Microservices/RidgeRun Services/Engagement Analytics (view source)
Revision as of 19:58, 26 March 2025
, 26 Marchno edit summary
Efernandez (talk | contribs) |
Efernandez (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
</noinclude> | </noinclude> | ||
RidgeRun's Engagement Analytics Service is in charge of managing people engagement statistics. It reads detection/direction messages from Redis and based on the given configuration it calculates the person engagement and then posts statistics in both Redis and InfluxDB. | RidgeRun's Engagement Analytics Service is in charge of managing people engagement statistics. It reads detection/direction messages from Redis and based on the given configuration it calculates the person engagement and then posts statistics in both Redis and InfluxDB. It also calculates a heatmap of engaged people's locations and posts it as a redis stream. | ||
The following picture shows a basic diagram of the service | The following picture shows a basic diagram of the service | ||