diff options
| -rw-r--r-- | img/logstash-img1.png | bin | 27064 -> 0 bytes | |||
| -rw-r--r-- | stasherpresent.slide | 38 |
2 files changed, 8 insertions, 30 deletions
diff --git a/img/logstash-img1.png b/img/logstash-img1.png Binary files differdeleted file mode 100644 index e7a70f8..0000000 --- a/img/logstash-img1.png +++ /dev/null diff --git a/stasherpresent.slide b/stasherpresent.slide index d23a837..f9e7aba 100644 --- a/stasherpresent.slide +++ b/stasherpresent.slide @@ -14,15 +14,7 @@ https://sillymon.ch .caption logstash logo from the [[https://www.elastic.co/products/logstash][official logstash site]] -* What is it? - -- Now a project of elastic -- Used to be log-focused - -.image img/logstash-img1.png - - -* What does it do? +* What is it and what does it do? "Centralize, Transform & Stash your data" @@ -35,6 +27,8 @@ https://sillymon.ch - "Filters" for cleaning and transforming - "Outputs" for archiving, alerting, monitoring, etc. +Using text-based formats as the data representation + * "Centralize, Transform & Stash" @@ -82,15 +76,6 @@ Custom configuration language } -* Some statistics - -- Written in Ruby -- ~25K LOC in 377 files -- 360+ contributors -- 7'600+ commits -- 7'000+ stars - - * Stasher @@ -113,7 +98,7 @@ Code available at 1. Interfaces 2. Manager -3. Unfinished stuff (error handling, registry and config parser) +3. Especially unfinished stuff: error handling, config parser and the Registry * Interfaces @@ -177,7 +162,6 @@ manager/manager.go * Main advantages over shell script - Error handling - - Declarative config @@ -207,9 +191,7 @@ manager/manager.go * Config parser - Currently only supports string literals (no arrays) - - Hand-written parser - - Uses the Registry to get the modules @@ -254,9 +236,7 @@ conf/init.go * Implemented modules - input: stdin, http - - filter: str(ing), http - - output: stdout, http @@ -268,14 +248,12 @@ conf/init.go - Watch input directories - Multiple modules for each main module - Proper (configurable?) error handling -- If else? -* Considerations +* Considerations & Conclusions -- "Dynamic" Plugins (Go 1.8!?) -- Use HTTP for everything? -- Better off with shell scripts? - Generality and error handling -- DSL/declarative vs. Programming language balance? +- Use HTTP for everything? +- Level of "declarativeness" in the configuration +- Still better off with shell scripts? |
