Re: infrae.wsgi questions

--===============7776023709330437209==
Content-Type: multipart/alternative; boundary=20cf303bfe04bb087104ad875ce9

--20cf303bfe04bb087104ad875ce9
Content-Type: text/plain; charset=ISO-8859-1

(and bringing this in to the list, thanks gmail)

On Thu, Sep 22, 2011 at 8:05 AM, Andrew Altepeter <[email protected]>wrote:

> Hi,
>
>>
>> > I was wondering if it is possible to permanently add ignored exceptions?
>> > For instance by using a product-config section in zope.conf or
>> something?
>> >
>>
>>    I think a ZCML directive would be nice for that. An exception is a
>> class, so that
>> would validate its path, and you could define it directly next to the code
>> where you
>> defined the exception.
>>
>>    I can surely add this.
>>
>
> That would be very nice!
>
>>
>>   If you have the error from the filesystem log, you have almost no
>> information, like no path,
>> no browser information, referrer or user or just anything. The information
>> you see through Zope
>> with the infrae.wsgi errorlog is exactly the same you have on the
>> filesystem log, logged, using
>> Python logging (so you could configure it to go through syslog and merge
>> all the feeds of your ZEO
>> clients on one server, configuration done in paster configuration file).
>>
> Yes indeed that is a nice advantage.  I hadn't thought of syslogging to a
> central log server.
>
>>
>>   We probably can add a more verbose mode for logging that would
>> completely dump the request with
>> it.
>>
> I know my team would _greatly_ appreciate it.  That would make it much
> easier to diagnose certain problems, as there are important clues to
> state-dependent errors currently missing from the infrae.wsgi log.
>
>>
>>    In 3.0 code sources errors are friendly logged in the same log than
>> infrae.wsgi,
>> with a complete list of parameters and default values given to it,
>> document and version
>> informations.
>>
> Ok, that also sounds like a nice improvement (logging params, defauls, doc
> and version).  I may have to look at back-porting that for our Silva 2.3.
>
> Thanks for your response,
> Andy
>

--20cf303bfe04bb087104ad875ce9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

(and bringing this in to the list, thanks gmail)<br><br><div class=3D"gmail=
_quote">On Thu, Sep 22, 2011 at 8:05 AM, Andrew Altepeter <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi,<div><div class=3D"gmail_quote"><div cla=
ss=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<div><br>
&gt; I was wondering if it is possible to permanently add ignored exception=
s?<br>
&gt; For instance by using a product-config section in zope.conf or somethi=
ng?<br>
&gt;<br>
<br>
</div> =A0 I think a ZCML directive would be nice for that. An exception is=
 a class, so that<br>
would validate its path, and you could define it directly next to the code =
where you<br>
defined the exception.<br>
<br>
 =A0 =A0I can surely add this.<br></blockquote><div><br></div></div><div>Th=
at would be very nice!=A0</div><div class=3D"im"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
<div><br></div>=A0=A0If you have the error from the filesystem log, you hav=
e almost no information, like no path,<br>
no browser information, referrer or user or just anything. The information =
you see through Zope<br>
with the infrae.wsgi errorlog is exactly the same you have on the filesyste=
m log, logged, using<br>
Python logging (so you could configure it to go through syslog and merge al=
l the feeds of your ZEO<br>
clients on one server, configuration done in paster configuration file).<br=
></blockquote></div><div>Yes indeed that is a nice advantage. =A0I hadn&#39=
;t thought of syslogging to a central log server. =A0</div><div class=3D"im=
">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<br>
 =A0 We probably can add a more verbose mode for logging that would complet=
ely dump the request with<br>
it.<br></blockquote></div><div>I know my team would _greatly_ appreciate it=
. =A0That would make it much easier to diagnose certain problems, as there =
are important clues to state-dependent errors currently missing from the in=
frae.wsgi log.=A0</div>
<div class=3D"im">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div><br>
</div> =A0 In 3.0 code sources errors are friendly logged in the same log t=
han infrae.wsgi,<br>
with a complete list of parameters and default values given to it, document=
 and version<br>
informations.<br></blockquote></div><div>Ok, that also sounds like a nice i=
mprovement (logging params, defauls, doc and version). =A0I may have to loo=
k at back-porting that for our Silva 2.3.=A0</div><div><br></div><div>Thank=
s for your response,</div>

<div>Andy</div></div></div>
</blockquote></div><br>

--20cf303bfe04bb087104ad875ce9--

--===============7776023709330437209==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
silva-dev mailing list
silva-dev-IAPFreCvJWM6s/[email protected]
https://lists.infrae.com/mailman/listinfo/silva-dev

--===============7776023709330437209==--