Playing with Elephants ~PostgreSQL and Pgpool-II~

Logging is an important topic and particularly useful for troubleshooting, debugging and monitoring. Many applications have their own built-in logging mechanism. Pgpool-II logging mechanism is similar to PostgreSQL logging mechanism. Pgpool-II log management system supports two ways for logging messages (stderr and syslog) and the logging collector process collects the logs sent to stderr and redirects them into log files. However, how can we manage the logging system on Kubernetes? In this blog, I will describe how to manage Pgpool-II container logs on Kubernetes. Logging on Kubernetes  Kubernetes supports the functionality to view the container logs by using “ kubectl logs ” command.  kubectl logs < pod name > However, logging on Kubernetes is complicated because the logs will be deleted when containers are terminated or recreated. Fluentd helps you to collect container logs and send the logs to desired destinations such as Amazon S3, MySQL, MongoDB, etc. How to use Fluentd