MySQL Bugs: #59719: Connector/PHP there is no log entry indicating aggr timeout

Bug #59719	Connector/PHP there is no log entry indicating aggr timeout
Submitted:	25 Jan 2011 16:20	Modified:	1 Feb 2011 12:20
Reporter:	Diego Medina	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Enterprise Monitor: Connector Plugins	Severity:	S3 (Non-critical)
Version:	1.0.1	OS:	Any
Assigned to:	Johannes Schlüter	CPU Architecture:	Any

Description:
If you enable the debug log on the php.ini file, and your aggregator is not running, you do not get any error on that log indicating the problem.

It would be better if the plugin would report an error if it cannot communicate with the aggregator. The connector/c does this

How to repeat:
1- Install and setup the connector/php
2- enable the debug log on the plugin
3- do not install an aggegator
4- run some queries using php and notice that the debug log tells you nothing about the problem

Thanks for the input. I can't find a worklog entry which describes what events/situations shall be logged in the debug logs of the various plugins. Can you create one?

Thus far my understanding of the debug log was that it shall show the HTTP requests that have been send and that is about it. 

You seem to be seeking for a solution to the problem that in the architecture of plugin - aggregator agent there is no '"test me"-button'. The lack of that "test me"-button should not been seen as defect of an individual plugin and its debug log. It is rather a distinct and forgotten feature.

We would be best off if we don't try to cure the lack of features, that could have been identified earlier, using a patch driven development approach. Every patch causes significant coordination efforts. 

Please take a step back and ask yourself:

 - what shall be reported in the log file (for every plugin)
 - is the log file the appropriate place for that event

It would be great if you summarized your finding in a worklog entry that we can work on for one of the next released.

Feedback provided to Johannes by email, setting back to verified.

I am sorry but this patch approach to software development takes too much time. The Connectors team does not have sufficient development resources to go for incomplete ad-hoc patches without asking ourselves what is behind this or that request. What is behind is something the software supplier and developer cannot decide on his own. It requires input from the one ordering the software.

Currently, whenever someone finds its time to try and test the plugin, he eventually spies a detail that seems worth to be changed and desired. Many such details come up because there is no proper planning and specification of the software before the implementation is done.

The time saved by not building an understanding of the software before the implementation starts is more than compensated by the time it takes afterwards to work on the bug reports. In sum we would be much faster, have much less bugs and would be much less frustrated, if we would sit down and specify requirements thoroughly. It would be cheaper for Oracle as a whole if the teams would sit down and use WorkLogs.

Setting to "To be fixed later".

In 2010 we agreed on a 1.0 TODO list for the PHP plugin. The Connectors team has constantly reported progress on it. The 1.0 tasks have been worked upon and are pretty much completed.

All new tasks shall go into 1.1 or later.

Please use https://intranet.mysql.com/worklog/Other/?tid=5785 to define the contents of a debug log. Make sure all plugin developers are involved. Once the WL is ready, we can implement it - for PHP, for C/C, for all the others.

This is Babulerman.

This bug is not scheduled to be fixed at this time.