PostgreSQL playground running on Docker with logs presented in Kibana dashboard and Pgadmin webinterface.
Install docker and docker-compose. Clone this repo to your local machine. Than start the containers:
docker-compose up[pgadmin]: http://pgadmin.docker.localhost/Database, username and password: postgres
docker exec -it dockerpostgresplus_postgres_1 sh (or docker-compose exec postgres sh)
su
docker-compose exec postgres psql -U postgres
wget https://s3.amazonaws.com/assets.datacamp.com/course/sql/dvdrental.zip; unzip dvdrental.zip
su postgres
psql
CREATE DATABASE sakila;
exit
pg_restore -U postgres -d sakila dvdrental.tar
docker-compose exec postgres bash /scripts/pglog.sh
yes "select * from public.film_actor;" | head -n 1000 | parallel "psql -U postgres -d sakila -c {1}"
psql> CREATE DATABASE pgbenchdb;
pgbench -i -s 50 pgbenchdb
pgbench -c 10 -j 2 -t 1000 pgbenchdb
To make sure all fields exist prior to importing the Kibana dashboard, run pgbench first.
URL: http://elasticsearch:9200 Access: proxy Index name: logstash- (daily pattern) Version: 5.x
# Check CPU consumption
$ docker stats $(docker inspect -f "{{ .Name }}" $(docker ps -q))
# Remove containers plus volumes
$ docker-compose down -v --remove-orphans --rmi all
# docker-compose Elasticsearch
Elasticsearch uses a hybrid mmapfs / niofs directory by default to store its indices. The default operating system limits on mmap counts is likely to be too low, which may result in out of memory exceptions. On Linux, you can increase the limits by running the following command as root:
One time:
$ sysctl -w vm.max_map_count=262144
Persistant:
$ echo 'vm.max_map_count=262144' >> /etc/sysctl.conf
