This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-21
Channels
- # announcements (1)
- # aws-lambda (62)
- # babashka (116)
- # beginners (67)
- # chlorine-clover (39)
- # cider (10)
- # cljs-dev (5)
- # clojure (30)
- # clojure-austin (2)
- # clojure-europe (2)
- # clojure-italy (6)
- # clojure-nl (24)
- # clojure-uk (28)
- # clojurescript (33)
- # data-science (6)
- # datascript (10)
- # datomic (5)
- # duct (39)
- # emacs (1)
- # events (8)
- # fulcro (9)
- # graalvm (29)
- # hoplon (7)
- # juxt (10)
- # malli (4)
- # off-topic (6)
- # pathom (10)
- # perun (1)
- # reagent (45)
- # shadow-cljs (5)
- # sql (14)
- # tools-deps (10)
- # xtdb (9)
@iagwanderson I’m not, but we do use a datadog sidecar in our ECS tasks
I cant understand what is happening, some clojure code is showing up correctly in the APM while others are in the env:none
and all requests to the pod shows up in a single internal dns address of the pod.
e.g. guarita-clj.production.svc.cluster.local:80/*
while it should be POST /something-else
I thought it could be the web framework used by these applications because some of them used httpkit
and others jetty
, I switched to jetty
in the broken ones, but nothing happened 😕