This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-15
Channels
- # aleph (14)
- # aws (5)
- # beginners (144)
- # bitcoin (1)
- # boot (14)
- # chestnut (13)
- # cljs-dev (58)
- # cljs-experience (1)
- # cljsrn (47)
- # clojure (107)
- # clojure-dev (9)
- # clojure-finland (12)
- # clojure-gamedev (4)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (5)
- # clojure-uk (28)
- # clojurescript (34)
- # cursive (9)
- # datomic (3)
- # emacs (11)
- # garden (16)
- # graphql (9)
- # hoplon (3)
- # jobs (2)
- # juxt (6)
- # off-topic (32)
- # om (10)
- # onyx (1)
- # pedestal (4)
- # proton (1)
- # re-frame (14)
- # reagent (8)
- # ring (1)
- # ring-swagger (34)
- # shadow-cljs (19)
- # sioux-falls (1)
- # spacemacs (16)
- # testing (14)
Curious to hear any opinions on approaches to log aggregation (sys/app/custom) from AWS-hosted systems; anyone using CloudWatch? Amazon's hosted ES? Trying to understand the benefits/drawbacks to using Amazon's offerings vs other service providers (eg Splunk, Sumo Logic).
CloudWatch logs works fine. Generally pretty straightforward to setup. It is what I would start with again if I were setting up log aggregation from scratch. It works well enough.
I haven’t used ES + things on top for log aggregation before though. I have used Splunk and really enjoyed it too. I moved to CloudWatch when I started a new company and wanted to get something up and running that had minimal moving parts and fit well with the AWS ecosystem. I’d make the same choice again.
At my company we are using http://logz.io (basically hosted ELK stack) for aggregation, it works fine but there are a bunch of deployment hoops to jump through to get it to work on AWS that I'd just as soon avoid. I find the CloudWatch UI to be aesthetically not very appealing. I've heard good things from other people though.