Go to file
Landon Dyck 802cbcf912 separate email from auth, improve config detection 2021-11-26 22:11:23 -06:00
pkg separate email from auth, improve config detection 2021-11-26 22:11:23 -06:00
.gitignore split client and golang api into separate repos 2021-11-26 16:08:14 -06:00
.woodpecker.yml fix woodpecker get and test 2021-11-18 16:43:27 -06:00
README.md save log entries from json input to sqlite db 2021-10-11 20:43:03 -05:00
dev.config separate email from auth, improve config detection 2021-11-26 22:11:23 -06:00
go.mod split client and golang api into separate repos 2021-11-26 16:08:14 -06:00
go.sum split client and golang api into separate repos 2021-11-26 16:08:14 -06:00
main.go separate email from auth, improve config detection 2021-11-26 22:11:23 -06:00

README.md

Mouseion collects log data from applications

Why? Other logging applications are:

  • Expensive. LogTail is one of the most affordable, and jumps to $30/month after their free tier.
  • Overcomplicated. Small software businesses don't need complex log analysis. They need access to the logs, usually within a period of time.
  • Difficult to get started. Self-hosting is a poorly-documented nightmare, and the load tools are even worse.

What Mouseion is:

  • Simple. Easy to set up, easy to load with data, easy to use
  • Affordable. Self-hostable, affordable hosted option
  • Efficient. Takes steps to reduce the storage for customer data (and pass that on to the customer)

What Mouseion is not:

  • Massively scaleable. I don't know how much Mouseion can handle right now, but it's probably not going to handle Facebook-level logging.
  • Machine-learning AI Smart Big Data Analytics. It's simple. It's not going to tell you how many times the word "cat" has appeared in your logs
  • Bloated. We're not going to implement all the features every business needs. Again, it's simple.

How it works:

  1. A source sends log data to the Mouseion server. The source sends the entry with a timestamp, the entry text, and a set of tags (if desired)
  2. The server stores those log entries, deduplicating as necessary.
  3. When something happens, you log in with the client and look at your entries by time and optionally by tag.
  4. You fix things and save the day.