Hi Jep,
create a file routes.py and in it
routes_onerror=[('*/*','/logging/default/index')]
and the create an app "logging" with a "controllers/default.py" that
does the following:
from gluon.admin import *
def index():
from restricted import RestrictedError
app, ticket_id = request.vars.ticket.split('/')
e = RestrictedError()
e.load(request, app, ticket_id)
print e.traceback
return 'ticket: %s' % request.vars.ticket
all tickets will be logged by the logging app.
On Dec 22, 8:21 am, jep <[email protected]> wrote:
> Massimo,
>
> Tnx for replying.
>
> > You can find requests logged in httpserver.log
> > What kind of logs would you like to see?
>
> > Massimo
>
> Basically, having a plain text version of the logs that are now send
> to the tickets in one big long file would be a nice start.
>
> The tickets are great, but during debugging, i tend to make so much of
> those tickets, and keep clicking around untill i get pain from using
> my mouse. (says more about me than web2py).
> I can imagine it would be great to have an option to have a "tail -f
> web2pydebug.log" running in a terminal to see the debugging
> information running over my screen while i reload a page with
> problems.
>
> It imagine it could also be an idea for the people who use web2py in
> production to configure web2py to log to their syslog server, so they
> can use their normal toolings for processing warnings and errorlogs.
>
> Not logging by default, i like the default behaviour to be clean.
> Just an option to switch on logging in a syslog standard way, or to a
> local logfile would be nice.
>
> Kind regards,
>
> Jean-Paul
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
