13. I bet you can think of more information sources
Zequi V´azquez @RabbitLair Information is Power
14. Too much information and no control
Zequi V´azquez @RabbitLair Information is Power
15. We need to transform information into data
Zequi V´azquez @RabbitLair Information is Power
16.
17. Identify our high level goals
Improve performance
Identify points of failure
Know users behavior
Be aware of SLAs observance
. . .
Zequi V´azquez @RabbitLair Information is Power
22. From bottom to top
Zequi V´azquez @RabbitLair Information is Power
23. Firewall & IDS/IPS metrics
Scanners (network, sqlmap, spiders)
Bruteforce attacks
Incoming and outcoming connections
Ip addresses, user agents and more
Identify and block (?)
Zequi V´azquez @RabbitLair Information is Power
24. Network metrics
Number of connections/rejections
Speed, bandwidth consumption, latency
Specially relevant on cloud environments
Zequi V´azquez @RabbitLair Information is Power
25. Infrastructure metrics
Monitorize all services on your system
Service response time & uptime
Consider scaling, prepare for peaks
Centralize logs: one log to rule them all
Zequi V´azquez @RabbitLair Information is Power
26. Cache metrics
Available memory & usage
Hit/Miss ratio
Evisceration ratio
Zequi V´azquez @RabbitLair Information is Power
28. PHP metrics
Number of threads
Memory per thread
Timeouts
Number of requests per second
Opcache usage
Zequi V´azquez @RabbitLair Information is Power
29. Application metrics
Plan error handling and messages smartly
Profiling: log request times
User behavior: It is not spying (?)
SQL queries
Zequi V´azquez @RabbitLair Information is Power