[Phpmyadmin-devel] GSoC - Server Stats

Marc Delisle marc at infomarc.info
Fri Apr 2 11:51:14 CEST 2010

Philip Frank a écrit :
> 2010/4/1 Marc Delisle <marc at infomarc.info>:
>> Philip Frank a écrit :
>>> 2010/4/1 Marc Delisle <marc at infomarc.info>:
>>>> Philip Frank a écrit :
>>>>> Hello everyone,
>>>>> I'm a student from Munich, Germany and stumbled across the GSoC Idea
>>>>> of collecting the data that is shown on the server status page and
>>>>> rendering them as graphs over time. I will apply in the next days,
>>>>> here is what I thought of implementing when I'm accepted:
>>>>> Data collection: In the past, I used rrdtool to collect stats on a
>>>>> server. Its datastore has a limited size - over time old entries get
>>>>> merged together and the data gets thinner, but is never completely
>>>>> deleted. Unfortunately, it is not very portable. Therefor, I would
>>>>> implement a similarily behaving datastore ontop of a mysql table. I
>>>>> think of storing each set of measures as a row and limit the number of
>>>>> total rows, making room for new entries by combining one pair of
>>>>> neighbouring old entries together.
>>>> Hi Philip,
>>>> so you plan that an external process will collect data? Please have a
>>>> look on this list archives, this was discussed a few days ago.
>>> Hi Marc,
>>> i thought the process could be triggered by a cron, but if that is not
>>> an option, historic data can not be collected, i guess. How about a
>>> live monitoring tool? I could create a visualisation of the ratios of
>>> the different query types. Constantly updating that with ajax would be
>>> nice, and maybe even collecting the data in the browser and plotting
>>> graphes.
>> As discussed on the list, asking users to setup cron is out of
>> phpMyAdmin's scope. Live monitoring tool is interesting.
>> --
>> Marc Delisle
>> http://infomarc.info
> Alright, that live monitoring could be awesome, too. The user could
> select what values should be measured, they would be constantly
> updated via ajax and it would be graphed with processing.js.
> The data could be stored as long as the browser window is open, so it
> could still be displayed on a time axis. At its best, one could just
> leave pma running in his browser while testing different
> configurations.
> With the html5 client storage, even saving snapshots persistently and
> comparing them could be done.
> How does this sound?

Before reading your post about "as long as the browser window is open" I
had the same idea.

About selecting what values should be measured, I think that this
interface should at least propose a list of the most popular things to
measure, to guide the admin. I guess that admins will want to use this
to find problems on their servers.

Marc Delisle

More information about the Developers mailing list