Este es mi blog. Hay otros muchos pero este es el mío.
A la izquierda los clientes, a la derecha las páginas que va entregando el servidor, la “raqueta del pong” representa al servidor atendiendo a cada cliente, y el nº que rebota junto con cada bola (petición) el código HTTP que devuelve. ¡Impresionante! ¡Yo quiero! :-D
¡Gracias Meiziu! ;-)
Many times the reason because a web server is slow and unresponsive is that it’s under “attack”, on purpose or not, by a bot. I’ve seen cases where Google Bot, bots from research engines from universities or some other kind of indexer were responsible for more than half the traffic of a site. These cases are not real DoS attacks, this traffic can be considered legitimate, but the result is that it brings the service down. You can instruct some of these bots not to visit your site so often, like Google Bot using the Google Webmaster Tools and the sitemaps and/or robots.txt files, but usually you can’t and have to consider filtering all this traffic at the firewall. But in any case, the first step is realizing that a single IP (or a couple of them) is responsible for most of your traffic, identifying this IP and using whois learn who it belongs to.
You can run something like this to list the top five IP addresses on your Apache’s access.log:
cut -d" " -f 1 access.log | sort | uniq -c | sort -nr | head -n 5
Últimos comentarios
RSS