Ticket #2397 (closed enhancement: invalid)

Opened 4 years ago

Last modified 4 years ago

Wish to have a logtail system on ispcp!

Reported by: rethus Owned by: nuxwin
Priority: normal Milestone: ispCP ω 1.0.7
Component: Tools Version: ispCP ω 1.0.5
Severity: Don't know Keywords: logtail


Hi @ all,

most time its recommended to turn off php-error-messages for security reasons. Now i have a good idea to do this, but leave the benefit of the messages.

For this we need a tool which tails Logfiles of each user. So if the user is loged into his ispcp-Account, he should open this tool (may named liveDebugger or simlar) which is a resizeable window which could optionaly set to get always be focus.

Into the Window working a little Ajax-script, which shows the debug-files of the User in realtime.

I have found such a scribt here: http://commavee.com/2007/04/13/ajax-logfile-tailer-viewer/

This is a very goog feature for developer, cause they could see any logfiles they need in realtime...

What u think about this?

Change History

comment:1 Changed 4 years ago by nuxwin

  • Owner set to nuxwin
  • Status changed from new to assigned

Hello ;

The tools as you describe is not really needed for ispCP. In development, we sets the display_errors parameter to true to show all errors. In production, all errors are already hidden. Also, I've created a set of new libraries for the logging purpose. These new libraries will be introduced with ispCP 1.0.6.

the new logger libraries will be able to write log in a logfile, mail, database, Firebug console...

Anyway, only the administrator should be able to see the real error messages. All other users should see an custom message that replace the real error . I've already committed a new ispCP_ExceptionHandler class that provides a handler to manage all uncaught exceptions. The logger libraries will be introduced later (test in progress).

comment:2 Changed 4 years ago by nuxwin

  • Status changed from assigned to closed
  • Resolution set to invalid

comment:3 Changed 4 years ago by nuxwin

Re ;

Ok, sorry after re-reading, I understand better what you want mean exactly. You want a log tool that can be launched from the ispCP frontend by any customers. So each customer can see any PHP errors that are raised by their own scripts, that are stored in their own DocumentRoot?.

That as you want can be very hard to integrate to the ispCP panel for the following reasons:

1. The generic log tool must know information about the customer logfile like the name and the path.

2. To be able to use this, the customers should have created a logfile and also, their scripts must be able to log the errors in the log file.

3. In addition, Joximu (see the forum thread) right about the issue of sharing password. If I'm the owner of a domain name (ispCP account), I want no necessarily give access to the panel for another developer but just an Ftp access.

To resume:

I think that this tool should not be integrated in ispCP. Customers are free to put a copy of this library in their own DocumentRoot? and use it.

I hope you understand my poor English here.

Ref. forum thread: http://isp-control.net/forum/thread-11048-post-83625.html#pid83625

Note: See TracTickets for help on using tickets.