Open Source Projects Europe

A new version of LocalStamp has made available. This new version launches also a Elastic Search + Kibana docker instance that allows digesting logs in an easier way.

This guide assumes that you have already installed in your machine the SDK for PaaS for SLA.

Checking that I have the proper LocalStamp docker image

First thing for using it is to check that you have the right LocalStamp version. In order to do so try to launch the LocalStamp with the script local-stamp-start.sh. Then check the messages appearing in the console. If they look in this way:

Local Stamp log in /tmp/local-stamp.log
Local Stamp workdir in /tmp/local-stamp
Local Stamp Started
Listening on port 8090

you still have the old version of LocalStamp. Contrarily, if you see something like:

Local Stamp log in /tmp/local-stamp.log
Local Stamp workdir in /tmp/local-stamp
Executing Logger in 172.17.0.3
Starting Kibana on port 5601
Local Stamp Started
Listening on port 8090

or any message informing that the eslap.cloud/elk:1_0_0 docker image is missing you have the proper LocalStamp.

Installing the proper LocalStamp image

The first thing you should if you have an old version of LocalStamp is to change it. In order to do so:

1. Check if a LocalStamp is installed. Use the command:

   docker images
   

   And take a look in the list checking if eslap.cloud/local-stamp:1_0_0 appears.

2. Stop LocalStamp if running.

3. Remove the current LocalStamp image as follows:

   docker rmi eslap.cloud/local-stamp:1_0_0
   

4. Install the new LocalStamp image as follows (from the SDK tools folder):

   ./runtime-tool.sh install -n eslap://eslap.cloud/local-stamp/1_0_0
   

   Once installed it's time to install Elastic Search + Kibana docker image.

Installing the proper Elastic Search + Kibana image

1. Usually you won't have it but first step will be to check if the eslap.cloud/elk:1_0_0 image is installed. You can do so with the first instruction of the previous list, but checking in this case for eslap.cloud/elk:1_0_0. In the case you have it already installed so you can stop. If not fo to the next step.

2. Install the new LocalStamp image as follows (from the SDK tools folder):

   ./runtime-tool.sh install -n eslap://eslap.cloud/elk/1_0_0
   

Running the LocalStamp and accessing Kibana

Once everything is properly installed you can already use the new version of the LocalStamp that makes use of Kibana for helping you to digest logs. So, the steps to be done are the following ones:

1. Start LocalStamp from SDK tools directory.

   ./local-stamp-start.sh
   

   Check that console message you see is as follows:

   Local Stamp log in /tmp/local-stamp.log
   Local Stamp workdir in /tmp/local-stamp
   Executing Logger in 172.17.0.3
   Starting Kibana on port 5601
   Local Stamp Started
   Listening on port 8090
   

2. Deploy a service as usual with LocalStamp.

3. Later on, once the service is deployed you can access the logs using Kibana. In order to do so open a web browser and access to the url:

   http://localhost:5601
   

   Wait until Kibana prepares everyhting and then enjoy yourself.