From: Ricardo Wurmus <rekado@elephly.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"John Kehayias" <john.kehayias@protonmail.com>,
guix-devel <guix-devel@gnu.org>,
guix-maintainers@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: anonymized nginx logs (was Re: Guix user statistics and upstream/downstream dependencies)
Date: Wed, 10 Jul 2024 22:15:49 +0200 [thread overview]
Message-ID: <8734oh80lm.fsf@elephly.net> (raw)
In-Reply-To: <87y169f5zy.fsf@gmail.com> (Simon Tournier's message of "Wed, 10 Jul 2024 20:37:21 +0200")
Simon Tournier <zimon.toutoune@gmail.com> writes:
> On Tue, 14 May 2024 at 07:57, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> We have detailed anonymized nginx logs of all downloaded substitutes
>> from Berlin, at least. If you are interested to use this data as a
>> source we could probably make it available to you since it's anonymized
>> (real IP addresses have been obfuscated).
>
> I just had a chat this afternoon with a colleague about massaging such
> data. Could I have access to them?
Do you want the plain log files or would the processed HTML report
(generated with goaccess) be sufficient? The latest report is on
ci.guix.gnu.org:/var/log/report.html.
--
Ricardo
next prev parent reply other threads:[~2024-07-10 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 5:13 Guix user statistics and upstream/downstream dependencies John Kehayias
2024-05-14 6:43 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-05-14 11:57 ` Maxim Cournoyer
2024-07-10 18:37 ` anonymized nginx logs (was Re: Guix user statistics and upstream/downstream dependencies) Simon Tournier
2024-07-10 19:45 ` Maxim Cournoyer
2024-07-10 20:15 ` Ricardo Wurmus [this message]
2024-07-11 8:44 ` Simon Tournier
2024-05-15 12:17 ` Guix user statistics and upstream/downstream dependencies Wilko Meyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734oh80lm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).