[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: logs aggregation



Origin docs are at https://docs.openshift.org/latest/install_config/aggregate_logging.html -- though https://github.com/openshift/origin-aggregated-logging/blob/master/deployer/README.md refers to some recent usability improvements that haven't made their way into the official docs yet.

There is some integration with the console UI (https://docs.openshift.org/latest/install_config/aggregate_logging.html#kibana) but I'm not sure it does exactly what you asked. However you can fairly easily have Kibana pull up all the logs by pod label, which you could choose to be the label your DC/RC uses to identify its pods. This would include pods that no longer exist and containers that have been restarted and lost historical logs.

On Wed, Jun 22, 2016 at 10:14 AM, Rich Megginson <rmeggins redhat com> wrote:
On 06/22/2016 07:05 AM, Philippe Lafoucrière wrote:
Hi,

Something would be very useful in the console: logs from all replicas aggregated in a single page.
This is particularly useful when several web servers are serving the same site, and we need to debug something (ala docker-compose).
We could do that with the latest graylog, but directly in the console would be a killer feature.

By "console" do you mean the origin UI console?  If so, how would you do that with graylog?
Have you tried using https://github.com/openshift/origin-aggregated-logging ?  This doesn't integrate with the origin UI console, but it does provide Kibana.


Thanks!
Philippe


_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]