Go to file
Landon Dyck 74678341f9
continuous-integration/drone/push Build is passing Details
create cache volume
2022-03-22 21:02:44 -05:00
deploy/scripts gotta sudo to restart a service 2022-01-15 23:27:56 -06:00
pkg make it more clear that we aren't billing yet 2022-02-23 16:29:54 -06:00
public/css add some better styling with milligram 2022-02-15 12:00:29 -06:00
.drone.yml create cache volume 2022-03-22 21:02:44 -05:00
.gitignore split client and golang api into separate repos 2021-11-26 16:08:14 -06:00
.woodpecker.yml try adding the go cache 2022-02-15 12:15:40 -06:00
README.md change public-facing name 2022-01-15 22:17:08 -06:00
dev.config change public-facing name 2022-01-15 22:17:08 -06:00
go.mod update dependencies 2022-02-08 21:32:41 -06:00
go.sum update dependencies 2022-02-08 21:32:41 -06:00
main.go change public-facing name 2022-01-15 22:17:08 -06:00

README.md

TinyHatchet 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 TinyHatchet 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 TinyHatchet is not:

  • Massively scaleable. I don't know how much TinyHatchet 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 TinyHatchet 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.