From: "Michael Ströder" <michael@stroeder.com>
To: galene@lists.galene.org
Subject: [Galene] Re: Logging
Date: Fri, 8 Jan 2021 18:34:00 +0100 [thread overview]
Message-ID: <d8dcff84-ce9b-b5f6-6d4d-84ad95966d81@stroeder.com> (raw)
In-Reply-To: <87o8hz796z.wl-jch@irif.fr>
On 1/8/21 4:13 PM, Juliusz Chroboczek wrote:
> Michael Ströder wrote:
>> I'd love to see more connection meta data in /stats so I can tell which
>> user has which problem:
>> - connection's IP address
>> - nick name / user name
>
> The stats page is deliberately anonymised.
Hmm, is the /stats page meant to be publicly available? It's definitely
not at my site and never will be (limited by IP addresses and
password-protected).
So I'd argue that in my case the IP addresses, user agent info and user
names are already visible in the logs for the same personnel like the
/stats page.
Could this be made configurable?
> Also, you cannot spy on a conversation without appearing in the user
> list even if you have op privileges, just like you cannot unmute a
> user.
Good.
>> I suspect most of the users' minor or major issues are caused by
>> problems with their local setup. And more information would help
>> tracking down those.
>
> Be assured that I am well aware that it complicates troubleshooting -- you
> can imagine how difficult it was in the early days, when Galène would
> misbehave during a department meeting with important people.
And the result clearly shows the advantage of this eat-your-own-dogfood
approach. :-)
>> FWIW: Did anyone look at admin/monitor page of Janus gateway?
>
> Perhaps you could publish a screenshot?
Too big/long for a screenshot. Also you can click into the connection
information.
Ciao, Michael.
next prev parent reply other threads:[~2021-01-08 17:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:38 [Galene] Logging Juliusz Chroboczek
2021-01-07 22:45 ` [Galene] Logging Michael Ströder
2021-01-08 0:35 ` Antonin Décimo
2021-01-08 12:40 ` Toke Høiland-Jørgensen
2021-01-08 13:28 ` Juliusz Chroboczek
2021-01-08 13:52 ` Toke Høiland-Jørgensen
2021-01-08 14:33 ` Michael Ströder
2021-01-08 15:13 ` Juliusz Chroboczek
2021-01-08 17:34 ` Michael Ströder [this message]
2021-01-08 18:00 ` Juliusz Chroboczek
2021-01-08 15:34 ` Juliusz Chroboczek
2021-01-08 19:34 ` Toke Høiland-Jørgensen
2021-01-08 19:56 ` Juliusz Chroboczek
2021-01-09 0:18 ` Toke Høiland-Jørgensen
2021-01-09 13:34 ` Juliusz Chroboczek
2021-01-10 13:47 ` Toke Høiland-Jørgensen
2021-01-10 15:14 ` [Galene] Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-10 15:23 ` [Galene] " Juliusz Chroboczek
2021-01-10 22:23 ` Toke Høiland-Jørgensen
2021-01-10 22:44 ` Dave Taht
2021-01-11 0:07 ` Juliusz Chroboczek
2021-01-11 0:20 ` Toke Høiland-Jørgensen
2021-01-11 0:28 ` Juliusz Chroboczek
2021-01-11 0:30 ` Dave Taht
2021-01-11 6:23 ` Dave Taht
2021-01-11 12:55 ` [Galene] Multichannel audio [was: Congestion control...] Juliusz Chroboczek
2021-01-11 17:25 ` [Galene] " Dave Taht
2021-01-11 13:38 ` [Galene] Re: Congestion control and WebRTC [was: Logging] Juliusz Chroboczek
2021-01-11 15:17 ` Toke Høiland-Jørgensen
2021-01-11 17:20 ` Dave Taht
2021-01-12 1:38 ` Juliusz Chroboczek
2021-01-10 15:17 ` [Galene] Re: Logging Juliusz Chroboczek
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
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8dcff84-ce9b-b5f6-6d4d-84ad95966d81@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.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