Skip to content
This repository has been archived by the owner on May 14, 2020. It is now read-only.

Introduce logging aggregation in Libero deployments #361

Open
giorgiosironi opened this issue Jan 10, 2020 · 1 comment
Open

Introduce logging aggregation in Libero deployments #361

giorgiosironi opened this issue Jan 10, 2020 · 1 comment
Labels
continuous delivery the ability to get changes of all types live, safely and quickly in a sustainable way

Comments

@giorgiosironi
Copy link
Member

giorgiosironi commented Jan 10, 2020

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 giorgiosironi added the continuous delivery the ability to get changes of all types live, safely and quickly in a sustainable way label Jan 10, 2020
@giorgiosironi
Copy link
Member Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
continuous delivery the ability to get changes of all types live, safely and quickly in a sustainable way
Projects
None yet
Development

No branches or pull requests

1 participant