HANIoT Time Series Service

---

Microservice responsible for time series on the HANIoT platform.

Main features:

• Timeseries/Intraday:
  • steps, calories, distance, active_minutes and heart rate.
• InfluxDB
• Message Bus Integration (RabbitMQ).

See the documentation for more information.

Prerequisites

• Node 12.0.0+
• InfluxDB 1.7+
• RabbitMQ 3.8.0+

---

Set the environment variables

Application settings are defined by environment variables.. To define the settings, make a copy of the .env.example file, naming for .env. After that, open and edit the settings as needed. The following environments variables are available:

VARIABLE	DESCRIPTION	DEFAULT
NODE_ENV	Defines the environment in which the application runs. You can set: test (in this environment, the database defined in INFLUXDB_URI_TEST is used and the logs are disabled for better visualization of the test output), development (in this environment, all log levels are enabled) and production (in this environment, only the warning and error logs are enabled).	development
PORT_HTTP	Port used to listen for HTTP requests. Any request received on this port is redirected to the HTTPS port.	4000
PORT_HTTPS	Port used to listen for HTTPS requests. Do not forget to provide the private key and the SSL/TLS certificate. See the topic generate certificates.	4001
SSL_KEY_PATH	SSL/TLS certificate private key.	.certs/server.key
SSL_CERT_PATH	SSL/TLS certificate.	.certs/server.crt
INFLUXDB_HOST	InfluxDB database hostname.	localhost
INFLUXDB_PORT	InfluxDB database port.	8086
INFLUXDB_PROTOCOL	InfluxDB database protocol. (http or https). For TLS connection, the protocol is https and client certificates are required: (INFLUXDB_CERT_PATH, INFLUXDB_KEY_PATH e INFLUXDB_CA_PATH)	http
INFLUXDB_NAME	InfluxDB database name.	haniot-timeseries
INFLUXDB_USER	InfluxDB username for authentication. If the host does not require authentication, the value of this variable will be ignored.	none
INFLUXDB_PASS	InfluxDB password for authentication. If the host does not require authentication, the value of this variable will be ignored.	none
INFLUXDB_CERT_PATH	InfluxDB Certificate path.	.certs/influxdb/cert.pem
INFLUXDB_KEY_PATH	InfluxDB Certificate Key path.	.certs/influxdb/key.pem
INFLUXDB_CA_PATH	InfluxDB Certificate of the Authentication entity (CA).	.certs/influxdb/ca.pem
RABBITMQ_URI	URI for connection to RabbitMQ. The URI specifications . For example: amqp://user:pass@host:port/vhost. When TLS is used for conection the protocol is amqps and client certificates are required (RABBITMQ_CERT_PATH, RABBITMQ_KEY_PATH, RABBITMQ_CA_PATH)	amqp://guest:guest @127.0.0.1:5672
RABBITMQ_CERT_PATH	RabbitMQ Certificate	.certs/rabbitmq/cert.pem
RABBITMQ_KEY_PATH	RabbitMQ Key	.certs/rabbitmq/key.pem
RABBITMQ_CA_PATH	RabbitMQ Certificate of the Authentication entity (CA).	.certs/rabbitmq/ca.pem

Generate Certificates

For development and testing environments the easiest and fastest way is to generate your own self-signed certificates. These certificates can be used to encrypt data as well as certificates signed by a CA, but users will receive a warning that the certificate is not trusted for their computer or browser. Therefore, self-signed certificates should only be used in non-production environments, that is, development and testing environments. To do this, run the create-self-signed-certs.sh script in the root of the repository.

chmod +x ./create-self-signed-certs.sh

./create-self-signed-certs.sh

The following files will be created: ca.crt, jwt.key, jwt.key.pub, server.crt and server.key.

In production environments its highly recommended to always use valid certificates and provided by a certificate authority (CA). A good option is Let's Encrypt which is a CA that provides free certificates. The service is provided by the Internet Security Research Group (ISRG). The process to obtain the certificate is extremely simple, as it is only required to provide a valid domain and prove control over it. With Let's Encrypt, you do this by using software that uses the ACME protocol, which typically runs on your host. If you prefer, you can use the service provided by the SSL For Free website and follow the walkthrough. The service is free because the certificates are provided by Let's Encrypt, and it makes the process of obtaining the certificates less painful.

Installation and Execution

1. Install dependencies

npm install    

2. Build

Build the project. The build artifacts will be stored in the dist/ directory.

npm run build    

3. Run Server

npm start

Build the project and initialize the microservice. Useful for production/deployment.

npm run build && npm start

Running the tests

All tests

Run unit testing, integration and coverage by Mocha and Instanbul.

npm test

Unit test

npm run test:unit

Integration test

npm run test:integration

Coverage test

npm run test:cov

Navigate to the coverage directory and open the index.html file in the browser to see the result. Some statistics are also displayed in the terminal.

Generating code documentation

npm run build:doc

The html documentation will be generated in the /docs directory by typedoc.

Using Docker

In the Docker Hub, you can find the image of the most recent version of this repository. With this image it is easy to create your own containers.

docker run haniot/timeseries-service

This command will download the latest image and create a container with the default settings.

You can also create the container by passing the settings that are desired by the environment variables. The supported settings are the same as those defined in "Set the environment variables". See the following example:

  docker run -d --rm \
  -e PORT_HTTP=8000 \
  -e PORT_HTTPS=8001 \
  -v $(pwd)/.certs:/etc \  
  -e SSL_KEY_PATH=.certs/server.key \
  -e SSL_CERT_PATH=.certs/server.crt \
  -e INFLUXDB_HOST=HOSTNAME \
  -e INFLUXDB_PORT=8086 \
  -e INFLUXDB_PROTOCOL=http \  
  -e INFLUXDB_NAME=haniot-timeseries \
  -e RABBITMQ_URI="amqp://guest:guest@HOSTNAME:5672" \
  --name haniot-timeseries \   
  haniot/timeseries-service

If the InfluxDB or RabbitMQ instance is in the host local, add the --net=host statement when creating the container, this will cause the docker container to communicate with its local host.

docker run --rm \
  --net=host \
  ...

To generate your own docker image, run the following command:

docker build -t image_name:tag .