libero / publisher

The starting point for raising issues for Libero Publisher
MIT License
16 stars 4 forks source link

Introduce logging aggregation in Libero deployments #361

Open giorgiosironi opened 4 years ago

giorgiosironi commented 4 years ago

kubectl logs provide logs of the stdout/stderr of Pods still alive in the system. New deployments can reset this state.

(Persistent)Volumes can also be set up to persist logs that are written to a file, but they are not necessarily easy to access without kubectl exec into the running Pod; they also have the same problem with multiple replicas that multiple servers have, as they are stored and accessed separately even if all part of the same application.

Definition of Done: introduce log aggregation infrastructure that allows administrators or developers to search and tail logs the application logs of a microservice.

Related

Tasks

giorgiosironi commented 4 years ago

Trick for multiple containers: use kubectl logs -lapp.kubernetes.io/instance=publisher--test.