Download as ODP, PPTX
![Monitoring: Why? « When I get on the homepage I have a blank page […] » « Seriously? One moment, checking […] » « We are aware of the problem, our engineers have found the solution. Everything will be back to normal in 5 minutes » « Hell! You're right!? »](https://image.slidesharecdn.com/apm-pinbaen-100204150405-phpapp02/75/PHP-applications-environments-monitoring-APM-Pinba-34-2048.jpg)
Uploaded byPatrick Allaert
PHP applications/environments monitoring: APM & Pinba
This document summarizes two PHP monitoring tools: APM (Alternative PHP Monitor) and Pinba. APM is a tool dedicated to error handling in PHP applications. It provides functions to retrieve error events and slow requests from a database. Pinba is focused on real-time performance monitoring. It allows setting timers and retrieving performance metrics like request time and memory usage. Both tools have low overhead and are open source alternatives to commercial monitoring solutions.
PHP applications/environments monitoring: APM & Pinba
- 1. PHP applications/environments monitoring:APM & Pinba Davide Mendolia - Patrick Allaert PHPBenelux Conference 2010
- 2.
- 3.
- 4.
- 5.
- 6.
- 7. Works at Tuenti
- 8. Social network ,based in Madrid
- 9. More than 20billion page views per month
- 10. First Spanish websiteahead Google, Microsoft and Facebook (Comscore)
- 11. International work environment(15 nationalities)
- 12.
- 13.
- 14.
- 15.
- 16. Works at eZ Systems (eZ Publish, eZ Components)
- 17. PHPBenelux staffmember ( http://www.phpbenelux.eu/ )
- 18. Patrick Allaert Startprogramming with PHP 3
- 19. Ten years ofFree Software evangelism
- 20. Contributions: PHP (ext/ldap,QA: PHPT)
- 21. KDESvn (Subversion clientfor KDE)
- 22. XOo°f (eXtensible OpenObject Oriented Framework)
- 23. Tabellio (collaborative suitefor parliamentary assembly)
- 24. Monitoring: Definition ? Beingaware of the state of a system by watching and measuring it.
- 25. Indicators: the physicalcondition of a machine
- 26. load of amachine
- 27.
- 28. the messages insystem logs
- 29.
- 30.
- 31. Monitoring: Why? Needin terms of increasing availability
- 32.
- 33.
- 34. Monitoring: Why? « WhenI get on the homepage I have a blank page […] » « Seriously? One moment, checking […] » « We are aware of the problem, our engineers have found the solution. Everything will be back to normal in 5 minutes » « Hell! You're right!? »
- 35. Monitoring: Presentation Monitoringthe P of LAMP. In particular: Error handling in PHP
- 36.
- 37. What are thesolutions ? Current: PHP
- 38. Zend Platform Newcomers:APM (Alternative PHP Monitor)
- 39.
- 40. PHP: integrated functionserror_reporting
- 41.
- 42.
- 43. syslog Windows =>event log set_error_handler()
- 44. Zend Platform All-in-Onecommercial solution of Zend. Includes: monitoring
- 45.
- 46.
- 47.
- 48. APM A lternative P HP M onitor
- 49. Dedicated on errorhandling
- 50. Born in october2008
- 51.
- 52. Why ? LAMP+ APC + Xdebug
- 53. Missing software buildingblock in the Free Software landscape.
- 54. Performance problems indirectlyrelated to the Zend Platform. Need of a solution with a minimum impact. + APM (LAMPAXA)
- 55.
- 56. Database event idINTEGER ts TEXT type INTEGER file TEXT line INTEGER message TEXT backtrace TEXT slow_request id INTEGER ts TEXT duration FLOAT file TEXT
- 57. PHP functions void apm_get_events ([int limit[, int offset[, int order[, bool asc[, bool json]]]]]) Prints events from the database in an HTML or JSON format. void apm_get_slow_requests ([int limit[, int offset[, int order[, bool asc[, bool json]]]]]) Prints slow requests from the database in an HTML or JSON format. int apm_get_events_count (void)
- 58.
- 59. Future PHP monitoringframework
- 60. Customizable strategies backends:SNMP (in progress)
- 61.
- 62. custom command Alternativestorage solutions: MySQL/MariaDB
- 63.
- 64.
- 65.
- 66. APM contact infoWebsites: http://pecl.php.net/package/APM/ http://code.google.com/p/peclapm/
- 67.
- 68.
- 69.
- 70. Pinba P HP i s n ot a b ottleneck a nymore
- 71. Dedicated to realtimeperformance monitoring
- 72.
- 73. Why ? LAMP+ APC + Xdebug + APM
- 74.
- 75. Missing software buildingblock in the PHP landscape.
- 76. Gather performance metricsin production environments. + Pinba
- 77.
- 78.
- 79. Data sent stringhostname – gethostname() result
- 80. int request_count –number of requests served by this process
- 81. string server_name –$_SERVER["SERVER_NAME"]
- 82. string script_name –$_SERVER["SCRIPT_NAME"]
- 83. int document_size –size of the response body
- 84. int memory_peak –memory allocation peak
- 85. float request_time –time spent of processing the request
- 86. float ru_utime –resource usage (user)
- 87. float ru_stime –resource usage (system)
- 88. array timers –array of timers (optional)
- 89. Benchmarking ? <?php$timer = microtime ( true ); // some code being benchmarked echo microtime ( true ) - $timer , "\n" ;
- 90. PHP functions resource pinba_timer_start (array tags[, array data]) Creates and starts new timer. bool pinba_timer_stop (resource timer) Stops the timer. bool pinba_timers_stop (void) Stops all running timers. bool pinba_script_name_set (string script_name) Set custom script name instead of $_SERVER['SCRIPT_NAME'] used by default.
- 91. PHP functions array pinba_timer_get_info (resource timer) Returns timer data.
- 92.
- 93. array(4) { ["value"]=>float(0.0213) ["tags"]=>array(1) { ["foo"]=>string(3) "bar" } ["started"]=>bool(true) ["data"]=>NULL }
- 94. PHP functions array pinba_get_info (void) Returns all request data (including timers user data).
- 95. Example: array(9) { ["mem_peak_usage"]=> int(786432) ["req_time"]=> float(0.001529) ["ru_utime"]=> float(0) ["ru_stime"]=> float(0) ["req_count"]=> int(1) ["doc_size"]=> int(0) ["server_name"]=> string(7) "unknown" ["script_name"]=> string(1) "-" ["timers"]=> array(1) { [0]=> array(4) { [...] } } }
- 96. Tables The Pinbaplugin provides two tables types: Raw data tables
- 97.
- 98. Raw data tablesrequest: Stores all the request data.
- 99. The table isa cyclic buffer of a certain size. timer: Stores timer data. tag: Stores unique list of tags and their IDs. timertag: Stores tag values.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116.
- 117.
- 118.
- 119.
- 120.
- 121. Tag(s) reports Tworeport types: « tag info »
- 122. « tag report » Bothof them being available for: 1 tag
- 123.
- 124. Tag info for1 tag Timer data grouped by the value of the specified tag. CREATE TABLE `tag_info_foo` ( `tag_value` varchar ( 32 ) DEFAULT NULL , `req_count` int ( 11 ) DEFAULT NULL , `hit_count` int ( 11 ) DEFAULT NULL , `timer_value` float DEFAULT NULL ) ENGINE =PINBA DEFAULT CHARSET =latin1 COMMENT = 'tag_info:foo'
- 125. Tag info for2 tags Timer data grouped by the value of two specified tags. CREATE TABLE `tag_info_foo_bar` ( `foo_value` varchar ( 32 ) DEFAULT NULL , `bar_value` varchar ( 32 ) DEFAULT NULL , `req_count` int ( 11 ) DEFAULT NULL , `hit_count` int ( 11 ) DEFAULT NULL , `timer_value` float DEFAULT NULL ) ENGINE =PINBA DEFAULT CHARSET =latin1 COMMENT = 'tag2_info:foo,bar'
- 126. Tag report for1 tag Timer data grouped by script name and value of the specified tag. CREATE TABLE `tag_report_foo` ( `script_name` varchar ( 128 ) DEFAULT NULL , `tag_value` varchar ( 32 ) DEFAULT NULL , `req_count` int ( 11 ) DEFAULT NULL , `hit_count` int ( 11 ) DEFAULT NULL , `timer_value` float DEFAULT NULL ) ENGINE =PINBA DEFAULT CHARSET =latin1 COMMENT = 'tag_report:foo'
- 127. Tag report for2 tags Timer data grouped by script name and value of two specified tags. CREATE TABLE `tag_report_foo_bar` ( `script_name` varchar ( 128 ) DEFAULT NULL , `tag1_value` varchar ( 32 ) DEFAULT NULL , `tag2_value` varchar ( 32 ) DEFAULT NULL , `req_count` int ( 11 ) DEFAULT NULL , `hit_count` int ( 11 ) DEFAULT NULL , `timer_value` float DEFAULT NULL ) ENGINE =PINBA DEFAULT CHARSET =latin1 COMMENT = 'tag2_report:foo,bar'
- 128. Performance Overhead +/-2 µs/request on a personal computer.
- 129. Invariable from theavailability of MySQL (Reminder: UDP protocol).
- 130. Pinba contact infoWebsite: http://pinba.org/
- 131.
- 132. Credits Andrei Nigmatulin- initial design and first implementation.
- 133. Alexey Rybak -design, ideas and lots of (useful) critics.
- 134. Special thanks toSergey Frolovichev.
- 135. Current implementation isdone by Antony Dovgal.
- 136.
Editor's Notes
- #7 Surveiller d'eventuellle erreur comportementale de l'application. Surveiller au niveau des performances, afin de prevoir d'eventuel probleme
- #12 Page de demo avec E_NOTICE et autre, Display avec tail
- #15 Tail -f /var/log/php/error.log Page vide de apm.php Puis generation d'une page d'erreur Affichage de apm.php Recommecer avec mutilple erreur
- #16 Rappel, qu'est ce que APC, Xdebug, … Compatbilité totale avec le monde du LL
- #24 Compatbilité totale avec le monde du LL
- #25 L'extension PHP Pinba envoie un paquet UDP lors de la terminaison d'une requête qui contient des informations comme: hostname - gethostname() result request_count - number of requests served by this process server_name script_name document_size - size of the response body memory_peak - memory allocation peak request_time - time spent of processing the request ru_utime - resource usage (user) ru_stime - resource usage (system) timers - array of timers (optional) De la nature UDP, aucune connexion n'est réalisée, ce qui permet d'avoir aucun impacte de performance, mais des pertes de paquets pourraient se produire. De l'autre coté, le plugin MySQL Pinba écoute sur le port configuré pour récupérer les paquets et les décoder afin de les stocker dans ses pools d'enregistrements ainsi que de mettre à jour les index, les rapports de bases et rapports de tags si ils existent.
- #32 Raw data tables contain raw request data (surprise!). Please bear in mind that access to the raw data is relatively slow (the number of records might reach millions and there are NO indexes except for primary keys, so almost any operation requires full table scan). Reports were created in order to speed up the most frequent operations by aggregating data on-the-fly, when new request data arrives.