3,072
edits
Efernandez (talk | contribs) No edit summary |
Efernandez (talk | contribs) No edit summary |
||
Line 8: | Line 8: | ||
</noinclude> | </noinclude> | ||
RidgeRun's | 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. | ||
The following picture shows a basic diagram of the service | The following picture shows a basic diagram of the service | ||
[[File:MicroservicesArchitecture- | [[File:MicroservicesArchitecture-EngagementAnalytics.png|800px|thumb|center]] | ||
The service can be configured using a configuration file or via REST API. | The service can be configured using a configuration file or via REST API. | ||
Line 23: | Line 21: | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
docker run -it --rm \ | |||
docker run | |||
-- | |||
- | |||
--network host \ | --network host \ | ||
- | --volume <path to directory containing your configuration file>:/configs \ | ||
--name | -e INFLUXDB_TOKEN=<your influx db token> \ | ||
ridgerun/ | --name engagement-analytics-service \ | ||
ridgerun/engagement-analytics-service:latest \ | |||
--host 0.0.0.0 \ | |||
--config-file /configs/<your configuration file name> \ | |||
--retry | |||
</syntaxhighlight> | </syntaxhighlight> | ||
This will run the | This will run the Engagement Analytics service in localhost using port 5053. Make the correct path to your configuration file and the proper configuration file name. | ||
}} | }} | ||
{{message|type=doc | {{message|type=doc | ||
|content= | |content= | ||
* [https://ridgerun.github.io/ | * [https://ridgerun.github.io/engagement-analytics-service/Service Documentation] | ||
* [https://ridgerun.github.io/ | * [https://ridgerun.github.io/engagement-analytics-service/api.html Api Documentation] | ||
<br> | <br> | ||
See [[Metropolis Microservices/Tools/API Usage|API Usage]] for an example of how to use the API documentation to control the service | See [[Metropolis Microservices/Tools/API Usage|API Usage]] for an example of how to use the API documentation to control the service |