LogBus

Put your logs on the bus and ship them to their happy place.

Using the terms "log" & "event" synonymously

Highlights

• animation of pipeline
• 1st class support for [de]multiplexing
  • tap, fan in, fan out easily
  • dynamically tap (eg to debug pipeline, temporarily increase verbosity downstream)
• plain ol' javascript
• a nice balance of scaling up and scaling down
  • throw more nodes at it
  • load balance, no need for cluster mgmt
  • a low-power cpu thread with 50MB of resident memory can do plenty

Example Use Cases

• BPM, [Node-RED](https://nodered.org) a better fit
• compliance, tap into log stream at required point and ship to secure location while other flows can process for more actionable events
• observability, using plain ol' javascript it is simple enough to consume metrics from other systems (see netdata example) as well as parse textual data for metrics (see web analytics example)

Compare To Other Log Processors

• DSL vs javascript, often times flow control is an after thought which leads to configurations that look more like messy DSL's
• poor [de]mux support, many systems assume a single flow or pipeline so you must run multiple instances which means more mgmt and a waste of resources reprocessing the same data multiple times
• focused on scaling up while logbus more focused on being a general purpose tool
• poor plugin story, more akin to web dev of the 90's where you simple plop in some javascript as opposed to web dev of today, plugins can be treated as simple functions in that they take an input (consume events) and/or return a value (emit events) and just like functions whatever side-effects you create complicate the story, can wire things up incorrectly