Hi Victor, I thought first part (point 1) could be formulated as completely separate task with its own Jira ticket. So I created the ticket here: https://issues.apache.org/jira/browse/FINCN-196 and added my feedback about it as separate comment (basically go ahead and send pull requests)
I think I don't fully understand your ideas about how you propose solving part two. Could you elaborate? Kind regards Juhan Kontakt Victor Romero (<[email protected]>) kirjutas kuupäeval R, 3. jaanuar 2020 kell 07:04: > Hi Juhan & Fineract folks, > > I was checking the Jira ticket for Fineract CN > https://issues.apache.org/jira/browse/FINCN-189 > > I think the logging and monitoring should be done in two parts: > > > 1. Check for the infrastructure availability - health check/readiness > 2. 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 > >
