2 comments

  • toomuchtodo 3 hours ago ago

    Interesting idea! I use Graylog community edition for something similar, where everything technology I operate emits a logging event and Graylog is the append only log. Did you consider a traditional logging solution for this use case? If so, what differentiates this from such an approach?

    https://graylog.org/free/

    • gilad 2 hours ago ago

      Thanks for the supportive comment. Graylog is a mature tool, with many more capabilities than dayfile offers. I'd emphasize Graylog's ability to handle volume, variety of sources - storage, search and response to events. dayfile's total volume, ingest and response is smaller, but more targeted - informative, yet limited events ("backup finished", "TODO xyz" + open/close feature). The tradeoff is size and complexity of the application itself. Graylog packages multiple Java applications - its server, OpenSearch for search, and MongoDB. dayfile is a single Python-based application and a single SQLite file you can export at any time. dayfile uses token-based access controls - a read token can be limited to an audience, and a feed can be filtered by tag and made public. One log can serve multiple audiences and views without exposing all of it.

      I can imagine these working together, processing + HTTP notifications from Graylog, into a post-processed, actionable event using dayfile.

      From your comment I assume you operate multiple systems; which events would you want in a short daily record, as opposed to the full log?