[FOLIO-2089] SPIKE: determine FOLIO log aggregation approach on AWS EKS Created: 10/Jun/19 Updated: 03/Jun/20 Resolved: 26/Jul/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | CP: ready for planning, CP: sprint 68 | ||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
Getting access to hosted FOLIO container logs on a single-server deployment where Okapi is managing the deployment hasn't really necessitated the need for a proper log aggregation strategy since Okapi provided much of this functionality. However, distributed container deployments across K8 pods and hosts by non-Okapi mechanisms combined with clustered instances of Okapi need a proper log aggregation strategy in order to provide easier access to log files and to correlate log events. There a few different options. The following link provides a fluentd-based approach to log file aggregation on AWS. Additionally, we should determine where to output and access logs. Possibilities include S3 buckets or an Elasticsearch datastore. |
| Comments |
| Comment by John Malconian [ 10/Jun/19 ] |
|
In addition to FOLIO container logs, there are also Rancher logs and EKS control plane logs that may need to be considered as well. |
| Comment by John Malconian [ 25/Jul/19 ] |
|
The easiest path forward is to implement a EFK logging stack (Elasticsearch to store and index the container logs, Fluentd to ship and aggregate container logs to Elasticsearch, and a Kibana dashboard to interface with logs). As it so happens there is a EFK stack helmchart that will install all components of the stack within the K8 cluster making installation fairly easy. There are a few customizations that need to made to deal with Ingress. Access the dashboard is open to the world, by default. I think we'd like to make those logs available to all members of Github folio-org. In order to do that we need to configure OAUTH integration with the NGINX ingress controller on the cluster and github.com/folio-org. The last step would be setting up some default dashboards in the Kibana UI. |
| Comment by John Malconian [ 26/Jul/19 ] |
|
Create
|