ltning<p>For any <a class="hashtag" href="https://pleroma.anduin.net/tag/mtcp" rel="nofollow noopener" target="_blank">#MTCP</a>, <a class="hashtag" href="https://pleroma.anduin.net/tag/dos" rel="nofollow noopener" target="_blank">#DOS</a> and <a class="hashtag" href="https://pleroma.anduin.net/tag/retrocomputing" rel="nofollow noopener" target="_blank">#Retrocomputing</a> nerds out there who are also running <code>httpserv</code> and want pretty graphs, poke me for a recipe for a hideosly bloated <a class="hashtag" href="https://pleroma.anduin.net/tag/logstash" rel="nofollow noopener" target="_blank">#logstash</a> configuration to ingest the UDP logs.</p><p>I feed it to <a class="hashtag" href="https://pleroma.anduin.net/tag/graylog" rel="nofollow noopener" target="_blank">#Graylog</a> which stores the data in <a class="hashtag" href="https://pleroma.anduin.net/tag/opensearch" rel="nofollow noopener" target="_blank">#Opensearch</a> - a pipeline that combined (and this is accurate) needs, conservatively, 4096 times as much RAM as the floppy museum itself (8MB).</p><p>And while looking at this when making this screenshot: I wonder why someone would hit http//floppy.museum with a <code>Referer</code>-header indicating they come from a salesforce-dot-com address? http-colon-slashslash-136.146.46.127 (about halfway down the list).</p><p><a class="hashtag" href="https://pleroma.anduin.net/tag/msdos" rel="nofollow noopener" target="_blank">#msdos</a> <a class="hashtag" href="https://pleroma.anduin.net/tag/bloatware" rel="nofollow noopener" target="_blank">#bloatware</a> <a class="hashtag" href="https://pleroma.anduin.net/tag/theremustbeabetterway" rel="nofollow noopener" target="_blank">#theremustbeabetterway</a></p>