Checking Service Execution Status in a Running Application

In an application or Event Process that is running, execution of individual microservices can be changed, that is, services can be stopped individually at runtime or some microservices could have stopped for some other reason. There are two ways to identify microservices that are not running, which are using.

• eStudio
• Web Console or Dashboard

Using eStudio

Log on to eStudio and click the running application that appears in bold. The application name will have the number of microservices running against the total microservices involved, at the end of the name, within brackets (like 3/4 written as seen in the figure below).

To identify the application that is not running, notice the names of the microservices present in the Event Process running in the Fiorano Orchestration editor. The stopped one appears in red colour font (names of running microservices appear in green font).

Using Dashboard

Status of the microservices in an application can be checked from the Fiorano Web Console, the Dashboard.

1. Log on to Dashboard present under Fiorano home directory and navigate to the Event processes tab under the Applications section in the left navigation panel.
2. Select the Show only running processes option or filter by typing the name of the event process.
3. Click the Details icon to check the status of the microservices running in that application.
   

   

4. Under the Service Instances panel, check the text mentioned under the Memory usage and Process ID columns where it notifies that the microservice that is not running. The text won't be in the bold green font as well.