Org Web Adapter

Editing journals/2021_05_12.org

:PROPERTIES:
:ID:       b3c350bd-e8a2-4cca-9bef-faae0b05e87f
:END:
#+title: 2021-05-12 - Wednesday

* Work
* Personal
* Timeline

- Note taken on [2021-05-12 Wed 14:11]

I had an [[id:44e5c8bf-85e8-4f47-a9f6-35dfe673e054][Engineering Culture]] thought today while watching [[id:08645fa5-463b-403e-945e-7986b526597e][Chris Pierce]]
  give a [[id:35513c71-23dc-4c5b-804e-83da89e03b01][Developer's Toolbox]] talk on DataDog and how the engagement product
  team is using the tool. He pulled up all the errors in the past few minutes
  and I wondered what our error logs in Kibana looked like. Turns out, there are
  a lot of them. I wasn't sure who's responsibility it is to fix those, and then
  I got thinking about Sentry errors and how hard it is to triage things.

So here it is. What if when we name loggers, we have loggers named for
  specific squads. So if we look up all the logs with the name
  `squad-partnership` they'll all show up in Kibana or Sentry or wherever. We
  already have a mod for squad ownership, so it could be defined in there. You
  could even use some funky namespace if you didn't want to lose the context of
  the module, though I think that module is there somewhere anyhow.