Requirements for Log Storage¶
Imported from Confluence
Content may be outdated. Verify before following any procedures. View original | Last updated: November 2022
| Requester | Feature | Use Case | Source of logs | Feasibility | Service/Solution | Is it Free? | Comments |
|---|---|---|---|---|---|---|---|
| Auto discovery applications in kubernates that should be connected to log platform | Developers should be able independently enable logs for applications running in EKS | Stdout of apps containers in Kubernates | Yes | 1. Filebeat 2. Loki Promtail | Yes | ||
| Retention period for logs. If we can have different retention periods for different log levels, we could have 3 days retention for INFO level and 2 weeks for WARN+ levels. | We cannot be prepared for when an issue might happen, so logs need to be constantly fetched and stored in case they will be needed. | STDOUT | |||||
| Querying logs using terminal | Although it is really nice to have something like Kibana to query the logs, some people still prefer the old good terminal. Also, for redundancy, if Kibana is ever down, we need a way to continue to query the logs | S3 files I assume |