1. PHP applications/environments monitoring: APM & Pinba Davide Mendolia - Patrick Allaert PHPBenelux Conference 2010

3. dmendolia@php.net or @davideme (Twitter)

4. Lead developer of APM

5. php-benchmark contributor

6. http://www.php-ci.net/

7. Works at Tuenti

9. More than 20 billion page views per month

10. First Spanish website ahead Google, Microsoft and Facebook (Comscore)

11. International work environment (15 nationalities)

12. Developers wanted!

14. patrickallaert@php.net or @patrick_allaert (Twitter)

15. Lead developer of APM

16. Works at eZ Systems (eZ Publish, eZ Components)

17. PHPBenelux staff member ( http://www.phpbenelux.eu/ )

19. Ten years of Free Software evangelism

21. KDESvn (Subversion client for KDE)

22. XOo°f (eXtensible Open Object Oriented Framework)

23. Tabellio (collaborative suite for parliamentary assembly)

26. load of a machine

27. application availability

28. the messages in system logs

29. network performance

30. known attacks

32. Economic reasons

33. User experience

34. 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!? »

36. Execution performance.

39. Pinba

41. display_errors

45. performance

46. high availability

47. …

49. Dedicated on error handling

50. Born in october 2008

51. APM demo !

53. Missing software building block in the Free Software landscape.

54. Performance problems indirectly related to the Zend Platform. Need of a solution with a minimum impact. + APM (LAMPAXA)

55. Architecture

56. Database event id INTEGER ts TEXT type INTEGER file TEXT line INTEGER message TEXT backtrace TEXT slow_request id INTEGER ts TEXT duration FLOAT file TEXT

58. int apm_get_slow_requests_count (void)

61. e-mail

63. Hadoop

64. Volatile backends

65. Contributing

67. Twitter: @php_apm

68. Mailing lists:

69. [email_address] [email_address]

71. Dedicated to realtime performance monitoring

72. Born in 2009

74. LAMPAXAP

75. Missing software building block in the PHP landscape.

76. Gather performance metrics in production environments. + Pinba

77. Architecture

78. Pinba demo!

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 , &quot;&quot; ;

92. Exemple:

93. array(4) { [&quot;value&quot;]=>float(0.0213) [&quot;tags&quot;]=>array(1) { [&quot;foo&quot;]=>string(3) &quot;bar&quot; } [&quot;started&quot;]=>bool(true) [&quot;data&quot;]=>NULL }

95. Example: array(9) { [&quot;mem_peak_usage&quot;]=> int(786432) [&quot;req_time&quot;]=> float(0.001529) [&quot;ru_utime&quot;]=> float(0) [&quot;ru_stime&quot;]=> float(0) [&quot;req_count&quot;]=> int(1) [&quot;doc_size&quot;]=> int(0) [&quot;server_name&quot;]=> string(7) &quot;unknown&quot; [&quot;script_name&quot;]=> string(1) &quot;-&quot; [&quot;timers&quot;]=> array(1) { [0]=> array(4) { [...] } } }

97. Reports

101. report_by_script_name;

102. report_by_server_name;

103. report_by_hostname;

104. report_by_server_and_script;

105. report_by_hostname_and_script;

106. report_by_hostname_and_server;

107. report_by_hostname_server_and_script.

109. req_per_sec;

110. req_time_total;

111. req_time_percent;

112. req_time_per_sec;

113. ru_utime_total;

114. ru_utime_percent;

116. ru_stime_percent;

117. ru_stime_per_sec;

118. traffic_total;

119. traffic_percent;

120. traffic_per_sec.

123. 2 tags

124. Tag info for 1 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 for 2 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 for 1 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 for 2 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'

129. Invariable from the availability of MySQL (Reminder: UDP protocol).

131. Mailing list: [email_address]

133. Alexey Rybak - design, ideas and lots of (useful) critics.

134. Special thanks to Sergey Frolovichev.

135. Current implementation is done by Antony Dovgal.

136. Questions ? Suggestions ?