anchor.diff:  
   ![SignalLevel](SignalLevel.jpg)
   
  -We went on to develop our own self service portal where you can send us a rating
  +We went on to develop our own self-service portal where you can send us a rating
   to our company chat as well as chasing the issue yourself. We've also open sourced
   it and you can get it [here](https://git.panter.ch/open-source/mikrotik_SS_java) and tinker with it however you like. 
   It should work on all [CapsMan](https://wiki.mikrotik.com/wiki/Manual:CAPsMAN) enabled Mikrotik Networks (make sure to
  
positive.code: 
  We started with an emergency setup (2 access points) because we had to move on
  faster than expected, there was not much of a concept, but it worked for us Panters
  who were pretty much alone at that time. While we were having our office on a
  construction site which was quite dusty at the time, we even managed to nearly
  kill our router because he suffocated in the dust (the whole rack was accidentally
  covered in dust) but it was nothing a little bit of compressed air couldn't solve.
  
negative.code: * [hAP ac](https://routerboard.com/RB962UiGS-5HacT2HnT) - like the wAP ac but with
  a built-in switch
  
  We were also pretty harsh when it comes down to kicking people out of our access points
  because if you got a bad connection, you're giving a bad time to all the other people
  using that access point. When we lowered the connectivity threshold to our sweet spot
  of 65dBm, we had an awesome connection, but somehow all the other users were having a
  bad time. This is the point you have to realize that you obviously have another perception
  of "things going well" (although you're right). At the moment we're having 20 AP's on 3
  floors, serving over 300 clients during peak hours.
  
  ![ClientsPerAP](ClientsPerAP.jpg)
  
  With all those different devices and total freedom for our coworkers, there are
  always some people having connectivity issues nonetheless, so the bigger we get,
  the more important is that we know how to monitor our network and how to distribute
  the load, that's hammering on our infrastructure.
  
  ![TrafficPerAP](TrafficPerAP.jpg)
  
  ## Monitoring
  As a sysadmin - responsible for something which quite a few people rely on every day, you
  should be able to tell someone where the problem comes from.
  So it's quite important to monitor your radio waves, so you can start investigating
  rising issues before a lot of people are affected by it and to troubleshoot specific
  clients' issues.
  