Follow these steps to prepare your setup for the demo:
-
The first change involves how you notify the
notifications-service
.When performing a request to the
notifications-service
you should add a new query parameter that is used to identify your group. For this purpose, a new file namedtoken
will be added to your group's one drive credentials folder. The contents of this file, is the value of thetoken
query parameter you have to pass when notifying thenotifications-service
.Additionally, you also have to change the host to which you are sending the request to
notifications-service.cec.4400app.me
.As such, when performing a request to the notifications-service, the url should look as follows:
https://notifications-service.cec.4400app.me/api/notify?token=<your-token>
.You can keep sending the body as you were.
-
Your REST API should be reachable at
<your-vm-ip>:3003
.This implies that when querying your REST API, the endpoints will be:
- Temperature:
http://<your-vm-ip>:3003/temperature?experiment-id=<experiment-id>&start-time=<start-time>&end-time=<end-time>
- Out-of-bounds:
http://<your-vm-ip>:3003/temperature/out-of-range?experiment-id=<experiment-id>
- Temperature:
-
Your prometheus instance should be reachable at
<your-vm-ip>:3008
. Make sure that your prometheus instance is exposing the metrics it is scraping from thenode_exporter
.Note: you only need the prometheus service from the local setup
docker-compose
file running, i.e., you don't need to have the grafana service running. -
A grafana instance is provided so you can view the current perceived state of your infrastructure.
Visit
https://grafana.cec.4400app.me
and login with the credentials provided in thegrafana
file in your group's credentials folder in one drive. -
Have your consumers read from the
experiment
topic instead of your group topic. The data produced throughout the demo will go to this topic.Note: Your group client only has read permissions on this topic, therefore you cannot run your producers to insert data into the topic.