From: "Carl Winbäck" <c@tunnel53.net>
To: supervision@list.skarnet.org
Subject: Re: Logging in a web server context
Date: Sat, 13 Jun 2020 13:17:15 +0200 [thread overview]
Message-ID: <CACsCw1PhyQp=Mv1s=f57E3Lrd7UK8Ja7zR-SLcJd109etj9k3A@mail.gmail.com> (raw)
In-Reply-To: <20200613105942.GA21613@klumpi.ignorelist.com>
On Sat, 13 Jun 2020 at 12:59, Jan Braun <janbraun@gmx.de> wrote:
> I'm not completely sure about s6, but runsv (from runit) hands only the
> stdout of the ./run script to the logger, and passes the stderr out of
> it's own stderr. This allows you to nest two runsv instances, one for
> each output channel:
>
> [...]
>
> Translation to s6 is left as an exercise to the reader.
Very interesting! I will study this example in depth in order to see
if it could be applied to s6.
If anyone has done this in s6, I would be interested to hear how you
achieved it.
> You could also run the webserver with stderr redirected to stdout, and
> let s6-log/svlogd filter the messages into one of two logdirs:
>
> $ printf 'stdout\nstderr\n' | s6-log -- '-.*err' t ./stdout f t ./stderr
> $ head std*/current
> ==> stderr/current <==
> @400000005ee4acd00efdfbe9 stderr
>
> ==> stdout/current <==
> @400000005ee4acd00efd6f5e stdout
>
> However, that's a brittle solution, because it relies on you creating
> correctly-matching filter rules. Depending on the webserver's output, it
> might still be feasible, but I recommend the other approach.
I agree that this method is not rock-solid since it relies on text
parsing. But for my purposes it would probably be sufficient.
Then I have at least one solution that should be feasible and possibly
both of them are.
Thank you Jan!
next prev parent reply other threads:[~2020-06-13 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 8:41 Carl Winbäck
2020-06-13 10:04 ` Casper Ti. Vector
2020-06-13 10:50 ` Carl Winbäck
2020-06-13 11:32 ` Casper Ti. Vector
2020-06-13 12:40 ` Carl Winbäck
2020-06-13 10:59 ` Jan Braun
2020-06-13 11:17 ` Carl Winbäck [this message]
2020-06-13 12:42 ` Laurent Bercot
2020-06-13 12:53 ` Laurent Bercot
2020-06-14 12:06 ` Carl Winbäck
2020-06-14 12:02 ` Carl Winbäck
[not found] ` <20200613100522.jvixsd6fnokz3fh2@bstg>
2020-06-13 12:17 ` Carl Winbäck
2020-06-13 12:30 ` Carl Winbäck
2020-06-13 18:51 ` Steve Litt
2020-06-13 19:29 ` yianiris
2020-06-15 4:19 ` Colin Booth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsCw1PhyQp=Mv1s=f57E3Lrd7UK8Ja7zR-SLcJd109etj9k3A@mail.gmail.com' \
--to=c@tunnel53.net \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).