Add metadata to all md files

docs/ansible/wiki/elk/fluentd.md

+---
+title: Ansible Wiki ELK Fluentd
+tags:
+- ansible
+---
 # Collecting Data
 
 Log data is being collected from all the log files in `/var/log` and all of its subdirectories as well as from certain listeners that can be configured on each host in the server farm to collect additional data from applications without piping them through the system log facilities first.

docs/ansible/wiki/elk/introduction.md

+---
+title: Ansible Wiki ELK Intro
+tags:
+- ansible
+---
 # ElasticSearch
 
 - [Introduction](elk/introduction)

docs/ansible/wiki/elk/kibana.md

+---
+title: Ansible Wiki ELK Kibana
+tags:
+- ansible
+---
 # UI to view the data
 
 ElasticSearch, which stores all our log data, has a powerful query language to access all of that data and do what ever you want to do with it. This is being used by e.g. [ElastAlert](monitoring/alerts-elk) to determine if any alerts have to be raised and there are a lot of other tools around that use that very same query language, e.g. a command line tool.

docs/ansible/wiki/firewall.md

+---
+title: Ansible Wiki Firewall
+tags:
+- ansible
+---
 # Firewall
 
 ## Overview of firewall protection

docs/ansible/wiki/gitlab-ci-configuration.md

+---
+title: Ansible Wiki CI Config
+tags:
+- ansible
+---
 If all the [preparation](gitlab-ci-prerequisites) has been completed, you only require a single file named `.gitlab-ci.yml` in the root of your repository.
 
 All the possible configuration is [documented by GitLab-CI](http://docs.gitlab.com/ce/ci/yaml/README.html)

docs/ansible/wiki/gitlab-ci-introduction.md

+---
+title: Ansible Wiki CI Intro
+tags:
+- ansible
+---
 GitLab-CI is an automated system on this host which is part of GitLab and documented in full detail on [gitlab.com](http://docs.gitlab.com/ce/ci/).
 
 This is utilized on this server such that the system administrator has to allocate one of the available runner to the projects that want to make use of it. Please contact @jurgenhaas should you be interested.

docs/ansible/wiki/gitlab-ci-prerequisites.md

+---
+title: Ansible Wiki CI Prerequisites
+tags:
+- ansible
+---
 # Preparing the GitLab-CI server
 
 As GitLab-CI is part of GitLab core, there is no extra software that needs to be installed. However, a few configuration steps are required:

docs/ansible/wiki/haproxy-custom-blacklists.md

+---
+title: Ansible Wiki HaProxy Custom Blacklists
+tags:
+- ansible
+---
 This Ansible suite comes with some default blacklists by default. However, in some circumstances it may be required to quickly add a couple of entries to those blackliste and you quickly want to rol them out.
 
 For this you can create/edit the file `/etc/ansible/facts.d/blacklist.fact` with this json content:

docs/ansible/wiki/haproxy-quick-update.md

+---
+title: Ansible Wiki HaProxy Quick Update
+tags:
+- ansible
+---
 If any changes have been made, e.g. new domains, changed aliases, or using SSL for certain domain, you might be looking for a way to quickly update HaProxy to make those changes effective.
 
 With the following command, everything will be done within seconds:

docs/ansible/wiki/hosts/add.md

+---
+title: Ansible Wiki Add Host
+tags:
+- ansible
+---
 # Adding a new host
 
 First of all, define all the variables for the new host in your inventory. Then, when working with static inventories, just add the details to the inventory file by adding the new hostname to all the groups that it belongs to.

docs/ansible/wiki/hosts/jiffybox.md

+---
+title: Ansible Wiki JiffyBox Host
+tags:
+- ansible
+---
 # Adding a new JiffyBox
 
 Login to your JiffyBox account at https://admin.jiffybox.de and add a new host by giving it a unique name, selecting a tarif and one of the Ubuntu distributions and defining a root password which is only going to be used for initial setup. It is recommended to use the same password which you have configured as your personal password in the Ansible vault.

docs/ansible/wiki/hosts/prevent-reboot.md

+---
+title: Ansible Wiki Host Prevent Reboot
+tags:
+- ansible
+---
 # Prevent the reboot of a host
 
 If you need to permanently or temporarily prevent a specific host from being rebooted you can achieve that by creating a file `/etc/ansible/facts.d/reboot.fact` with the following content:

docs/ansible/wiki/index.md

+---
+title: Ansible Wiki
+tags:
+- ansible
+---
 This repository is a framework around Ansible to make the daily usage more simple and straight forward. In this Wiki we're going to describe the usage of the main parts of it and show use cases on how you can get the most out of it.
 
 The following instructions assume that you've created the shortcuts as described on the modules installation instructions on the front page. If not, please adjust the commands below accordingly.

docs/ansible/wiki/inventory/add.md

+---
+title: Ansible Wiki Inventory Add
+tags:
+- ansible
+---
 # Adding a new inventory
 
 When adding a new inventory, there need to be one or more [GitLab runners](ansible/roles/gitlab-runner) installed and configured on one or more hosts within that host farm. Here is the step by step instruction on how to get this done:

docs/ansible/wiki/inventory/chatops.md

+---
+title: Ansible Wiki Inventory ChatOps
+tags:
+- ansible
+---
 # Triggering pipelines through ChatOps
 
 When logging into [Mattermost](https://mattermost.lakedrops.com) and going to the private channel of one of the inventories, you can trigger ChatOps commands for that inventory by typing `/[inventory] help`. This will show you a list of all available commands.

docs/ansible/wiki/inventory/pipelines.md

+---
+title: Ansible Wiki Inventory Pipeline
+tags:
+- ansible
+---
 # Scheduled pipelines
 
 Instead of cronjobs for individual maintenance tasks, we now use scheduled pipeline within GitLab in order to get

docs/ansible/wiki/letsencrypt.md

+---
+title: Ansible Wiki LetsEncrypt
+tags:
+- ansible
+---
 # LetsEncrypt SSL Certificates
 
 To regularely renew all certificates from LetsEncrypt on all hosts, execute this:

docs/ansible/wiki/monitoring/alerts-elk.md

+---
+title: Ansible Wiki Monitoring Alerts ELK
+tags:
+- ansible
+---
 # ElasticSearch Alerts
 
 To define rules for ElastAlert you can configure a list called `elastalerts` in your inventory.

docs/ansible/wiki/monitoring/alerts-netdata.md

+---
+title: Ansible Wiki Monitoring Alerts NetData
+tags:
+- ansible
+---
 # NetData Alerts
 
 NetData comes with a list of [preconfigured alerts][1] that we currently use as they come out of the box (not all of them apply to the server farm):

docs/ansible/wiki/monitoring/alerts-uptime.md

+---
+title: Ansible Wiki Monitoring Alerts Update
+tags:
+- ansible
+---
 # Uptime Alerts
 
 [Uptime][1] is a fork of the original and no longer maintained project from [fzaninotto][2] and got maintained and enhanced on its new home.