Error Reporting

[xLink]

I am proposing a call home function, the main purpose of this will be to log any errors in a single install of CSCMS to a local & remote database. The call home function should be toggleable upon install, and in the main Admin panel.

The idea being, that it gives the developers of the CMS a head start when errors start popping up after a new release or when a specific vulnerability has been caught. It gives us the ability to replicate the error in as much detail as needed & keep an eye on the errors as a whole. Single hit errors would more than likely be bots or malicious software pinging site urls trying to provoke a request, as such it shouldnt be till the errors gained significant popularity on the database that we would look into it.

Thoughts?

[MantisSTS]

You could have a 'count' column in the DB to to indicate how often the error is hit.

Also how do you propose to implement this? RESTful?

[xLink]

no need for a count column, the count would probably be sorted by teh query itself, and the implementation of it dosent really matter as long as we put steps in place to protect it against bitches loving errors

[MantisSTS]

Reason why I say have a count column is so it can easily be ordered by highest priority.

[NoelDavies]

I propose this isn't specifically part of the CMS, as it could kill apache if done too much; and that infact, it should be written in a self-encapsulating sever like NodeJS.

That way it's Async, we can serve requests at a scarily fast rate, and it won't affect the CMS.

[xLink]

& yeah richie, but dosent need the column, mysql can group em & count em on the fly, no sense in hardcoding it