This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-24
Channels
- # aws (2)
- # babashka (27)
- # beginners (97)
- # calva (1)
- # cherry (12)
- # cider (6)
- # clara (12)
- # clj-kondo (24)
- # clj-on-windows (4)
- # cljfx (14)
- # clojure (54)
- # clojure-australia (3)
- # clojure-europe (26)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojure-uk (9)
- # clojurescript (65)
- # conjure (5)
- # cursive (7)
- # datomic (18)
- # emacs (6)
- # helix (2)
- # honeysql (1)
- # jobs (1)
- # joyride (15)
- # kaocha (2)
- # lsp (10)
- # malli (5)
- # nbb (12)
- # observability (5)
- # off-topic (5)
- # reitit (2)
- # releases (4)
- # ring (1)
- # sci (17)
- # shadow-cljs (34)
- # testing (29)
- # tools-deps (45)
- # vim (7)
- # xtdb (6)
Does anyone have a good way on how to separate business and technical logging? I am using an EFK-stack and buisness-logs are just interleaved with technical logs. I wonder what way I can separate them and if I need a second EFK-stack then. In the end I want our support teams to be able to access Kibana and their dashboards but they should not see the technical logs.
You could probably set up a custom dashboard in kibana that filters out the technical stuff and share a permalink to that with your support team, a second stack for what's effectively a filter seems like overkill https://www.elastic.co/guide/en/kibana/current/reporting-getting-started.html
You could also redirect to different outputs based on a particular key (json field) using eg. rewrite_tag_filter rules and labels.
I recommend using mulog too. Logs would be in an easy format to filter and could easily add a key (or keys) that made the distinction between what is perceived as technical and business information I would keep all the events in one source, as the tech team can more readily connect business issues with technical activities