un bon compromis :)

Le lien donne vers la source de l'imagep oru la visibilité réelle, ici la visibilité "enhanced" :

https://scontent-a.xx.fbcdn.net/hphotos-frc1/t1/1623206_759824800705200_1272962792_n.jpg

We run bitly split across two data centers, one is a managed environment with DELL hardware, and the second is Amazon EC2.

Fork Rate. A strange configuration issue caused processes to be created at a rate of several hundred a second rather than the expected 1-10/second. 
Flow control packets.  A network configuration that honors flow control packets and isn’t configured to disable them, can temporarily cause dropped traffic.
Swap In/Out Rate. Measure the right thing. It's the rate memory is swapped in/out that can impact performance, not the quantity. 
Server Boot Notification. Use an init script to capture when servers are dying. Servers do die, but are they dying too often? 
NTP Clock Offset. If you are not checking one of you servers is probably not properly time synced. 
DNS Resolutions. This is a key part of your infrastructure that often goes unchecked. It can be the source of a lot of latency and availability problems. On the Internal DNS check quantity, latency, and availability. Also verify External DNS servers give the correct answers and are available. 
SSL Expiration. Don't let those certificates expire. Set up an expiration check.
DELL OpenManage Server Administrator (OMSA).  Monitor the outputs from OMSA to know when failures have occurred. 
Connection Limits. Do you know how close you are to your connection limits?
Load Balancer Status. It's important to have visibility into your load balancer status by making the health stats visible.

de la bonne doc

fournir un gdb a faire

ouh ça va envoyer apache enversion 2.4, nginx doit trembler !

Une fois que j'aurais fini mon petit setup a moi j'irias peut être ailleurs :) mais bon le support est super cool compétent et ils rechignent pas à filer des mois gratuits !
Pour IPredator :

1. We keep connection logs for debugging purposes, which happens encrypted and off-site. Connection logs contain information for debugging PPTP client issues. We try to store the least amount legally possible anywhere. IP-addresses are encrypted and can only be decrypted by non-support staff to ensure a proper process. For example, to work around issues where the police ruffles up the support staff a bit to get data for an abuse report. In the database we only store the details users give us on sign-up and a limited backlog of payments.

2. Sweden.

3. Usually we only receive email, therefore we drop anything that has DMCA in the subject. If they want something they need to send us a letter or a fax or send the police. Most of the time we get complaints for running the TPB proxy or the TOR servers.

4. PaySafe, BitCoins, PayPal, PaySon, AlertPay

sinon, je rogne sur le budget écran :D