Hi Roberto and Łukasz
It all sounds good. I am not a desperate hurry to integrate into Sentry so Ill hang fire until the "exceptions" framework is out. I'm sure it will be worth the wait. Having a Sentry plugin built into uWSGI would be great. If key vars such as %n could be mapped into the raven payload using the excellent uWSGI config system, we would have a very flexible logging solution indeed. Below is just me thinking out loud as to how the sentry plugin config might look: There could be a scenario where users would like the events generated by all Vassals under an Emperor to be sent to a single Sentry 'project'. Or the users might want to map each Vassal to a specific Sentry 'project'(numeric) Ether way this could be handled by config inheritance, as so. # file: common.ini stats = /tmp/uwsgi.%(project).stats.socket . sentry-dsn = https://public_key:[email protected]/%(project_id) sentry-capture-extra = %(sentry_extra) . . # file: vassal_projectX.ini project = %n project_id = 1 sentry_extra = 'Some useful info about this app. Foo' ini = common.ini . . I wish you good luck with the "exceptions" framework development task. And as has been said may times before, but cant be said enough, thanks for the time and effort you put into uWSGI. Dave On 10 June 2013 11:00, <[email protected]> wrote: > Send uWSGI mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of uWSGI digest..." > > > Today's Topics: > > 1. Sending uWSGI errors and events to Sentry ? (Dave Coutts) > 2. Re: Sending uWSGI errors and events to Sentry ? (Roberto De Ioris) > 3. Re: Sending uWSGI errors and events to Sentry ? (?ukasz Mierzwa) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 9 Jun 2013 21:27:44 +0100 > From: Dave Coutts <[email protected]> > To: [email protected] > Subject: [uWSGI] Sending uWSGI errors and events to Sentry ? > Message-ID: > < > capy64o96o+dkb+fpevjbhmbr8cdbarohktqm49fhfrhzbro...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > > Has anybody on the list implemented a solution to send uWSGI errors and > events to Sentry? > > I have a Nginx->uWSGI->Flask stack. > The Flask apps log to Sentry via the raven module. > uWSGI logs to a singular log file for the Emperor, and separate log files > per Flask app vassal. > > What I would like to be able to do is send Emperor and Vassal uWSGI events > to Sentry. > By event I mean restarts, mode changes and errors. > > I think the basic building blocks are available for a zeromq bridge based > solution in, > http://uwsgi-docs.readthedocs.org/en/latest/Options.html#log-zeromq > and > > https://github.com/getsentry/raven-python/tree/master/raven/contrib/transports/zeromq > With the event structure being described here, > http://raven.readthedocs.org/en/latest/usage.html > > > I thought I would ask the list if a raven-uwsgi type solution already > existed before I have a look at cobbling a solution together myself. > > Thanks > > Dave > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.unbit.it/pipermail/uwsgi/attachments/20130609/85d77d29/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Mon, 10 Jun 2013 05:25:17 +0200 > From: "Roberto De Ioris" <[email protected]> > To: "uWSGI developers and users list" <[email protected]> > Subject: Re: [uWSGI] Sending uWSGI errors and events to Sentry ? > Message-ID: > <[email protected]> > Content-Type: text/plain;charset=utf-8 > > > > Hi > > > > > > Has anybody on the list implemented a solution to send uWSGI errors and > > events to Sentry? > > > > I have a Nginx->uWSGI->Flask stack. > > The Flask apps log to Sentry via the raven module. > > uWSGI logs to a singular log file for the Emperor, and separate log files > > per Flask app vassal. > > > > What I would like to be able to do is send Emperor and Vassal uWSGI > events > > to Sentry. > > By event I mean restarts, mode changes and errors. > > > > I think the basic building blocks are available for a zeromq bridge based > > solution in, > > http://uwsgi-docs.readthedocs.org/en/latest/Options.html#log-zeromq > > and > > > https://github.com/getsentry/raven-python/tree/master/raven/contrib/transports/zeromq > > With the event structure being described here, > > http://raven.readthedocs.org/en/latest/usage.html > > > > > > I thought I would ask the list if a raven-uwsgi type solution already > > existed before I have a look at cobbling a solution together myself. > > > > Thanks > > > > Dave > > > > We are working on the "exceptions" framework. Its main purpose will be > sending exceptions to external systems. > > Currently there is the "airbrake" (a sentry equivalente for the ruby > world) plugin already available but it only support the "alarm" framework. > > More will come soon. > > In the mean time i suppose you can use the "python" logger to send event > via python-raven. > > To enable the python logger just define a logger class in your WSGI class > and than add > > --logger python: > > for the default logger > > --logger python:foobar > > the the "foobar" one > > -- > Roberto De Ioris > http://unbit.it > > > ------------------------------ > > Message: 3 > Date: Mon, 10 Jun 2013 10:24:55 +0200 > From: ?ukasz Mierzwa <[email protected]> > To: uWSGI developers and users list <[email protected]> > Subject: Re: [uWSGI] Sending uWSGI errors and events to Sentry ? > Message-ID: > < > cafcbevswpyygbryav9j2no_cfzwgzvdf4f5rc5moeod0crs...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-2" > > I could add sentry support, but first we should move exceptions handling > forward. So far, every time I want to make some planning around it I get > stuck, I'll try to work on it this week. > > > 2013/6/10 Roberto De Ioris <[email protected]> > > > > > > Hi > > > > > > > > > Has anybody on the list implemented a solution to send uWSGI errors and > > > events to Sentry? > > > > > > I have a Nginx->uWSGI->Flask stack. > > > The Flask apps log to Sentry via the raven module. > > > uWSGI logs to a singular log file for the Emperor, and separate log > files > > > per Flask app vassal. > > > > > > What I would like to be able to do is send Emperor and Vassal uWSGI > > events > > > to Sentry. > > > By event I mean restarts, mode changes and errors. > > > > > > I think the basic building blocks are available for a zeromq bridge > based > > > solution in, > > > http://uwsgi-docs.readthedocs.org/en/latest/Options.html#log-zeromq > > > and > > > > > > https://github.com/getsentry/raven-python/tree/master/raven/contrib/transports/zeromq > > > With the event structure being described here, > > > http://raven.readthedocs.org/en/latest/usage.html > > > > > > > > > I thought I would ask the list if a raven-uwsgi type solution already > > > existed before I have a look at cobbling a solution together myself. > > > > > > Thanks > > > > > > Dave > > > > > > > We are working on the "exceptions" framework. Its main purpose will be > > sending exceptions to external systems. > > > > Currently there is the "airbrake" (a sentry equivalente for the ruby > > world) plugin already available but it only support the "alarm" > framework. > > > > More will come soon. > > > > In the mean time i suppose you can use the "python" logger to send event > > via python-raven. > > > > To enable the python logger just define a logger class in your WSGI class > > and than add > > > > --logger python: > > > > for the default logger > > > > --logger python:foobar > > > > the the "foobar" one > > > > -- > > Roberto De Ioris > > http://unbit.it > > _______________________________________________ > > uWSGI mailing list > > [email protected] > > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > > > > -- > ?ukasz Mierzwa > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.unbit.it/pipermail/uwsgi/attachments/20130610/0e4514bf/attachment-0001.html > > > > ------------------------------ > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > End of uWSGI Digest, Vol 45, Issue 16 > ************************************* >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
