[
https://issues.apache.org/jira/browse/FINCN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007232#comment-17007232
]
VICTOR MANUEL ROMERO RODRIGUEZ commented on FINCN-189:
------------------------------------------------------
Hi Juhan & Fineract folks,
I think the logging and monitoring should be done in two parts:
# Check for the infrastructure availability - health check/readiness
# Check for the health and gather information of each Microservice for feeding
the logging and monitoring applications like Prometheus, ELK, Splunk or APM
like AppDynamics.
For each Docker container we have done a quick solution for checking if the
availability of each service, not only the TCP port checking but for the
database readiness or the backend on the other side of the middleware messaging.
Initially we have done the improvement for point 1 here:
[https://github.com/fintecheando/fineract-cn-docker-compose]
[https://github.com/itzamnamx/fineract-cn-lang-security-docker]
[https://github.com/itzamnamx/fineract-cn-provisioner]
[https://github.com/fintecheando/fineract-cn-identity]
What we have done is using the docker segmentation of the services and the
dependency verification for the startup. We have tested this in our local dev
and works. If this is Ok, please assign me this ticket so then I will send the
PRs to the Fineract repositories.
For point 2 we have used Spring boot actuator for accomplish the task but is
required to have the Logging and Monitoring tools enabled, we prefer to use ELK
or Prometheus.
Let me know your thoughts.
Regards
Victor Romero
> Add /health endpoint to each micro service
> ------------------------------------------
>
> Key: FINCN-189
> URL: https://issues.apache.org/jira/browse/FINCN-189
> Project: Fineract Cloud Native
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
> Labels: volunteer
>
> In order to run Fineract-CN micro services in production we need to know
> about each service if it is running or failing.
> For this we need to create /health endpoints to each micro service. If anyone
> turns to this endpoint the program code checks if it can access Postgres and
> Cassandra and if yes it responds back "UP", otherwise "DOWN".
> I recommend starting with Identity micro service because this micro service
> doens't depend on any other micro service (to run it you only need to have
> Cassandra and Postgres running).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)