Week 7 #2590
Week 7 #2590
Conversation
|
Hi @chrissap543 I cannot find the venue of the paper. Even though it is interesting, it is not good for this task. @algomaster99 could you share your thoughts on this as well? |
|
I agree with you, @sofiabobadilla ! The topic is more relevant for Infrastructure as code week. Moreover, the paper is more of a tutorial than a scientific paper. A scientific paper is supposed to tell a problem and probably a solution for it. @chrissap543 sorry for being so late in responding. Would it be okay if you can present something else? |
|
We understand; we have two backup papers we are interested in. We would like to do the first one more but if it isn't good, then we'll do the second. The first is A Survey on Deploying Prometheus and Grafana for Application Monitoring and the second is A Survey on Observability of Distributed Edge & Container-Based Microservices. Would it be possible to present on Thursday instead of Wednesday so we have ample time to prepare? |
|
@chrissap543 the second one is good. Yes, you can present on Thursday. Please submit a PR for that. I will close this. |
Assignment Proposal
Title
ELK: A Cohesive Logging Toolchain
Names and KTH ID
Deadline
Category
Description
The paper "Building a real-world logging infrastructure with Logstash, Elasticsearch and Kibana" writes about how a company was having difficulty merging log files between all of their micro-services. They rectified this problem using ELK.
Relevance
This paper is relevant because it details step-by-step how to create your own logging infrastructure. ELK is a widely used open-source toolchain for merging logs into more human-readable formats.