|
so does OpenTracing do everything prometheus does, or should i be running some combination of OpenTracing + logging + metric collection? like is there some tracer i can plug into OpenTracing to make it pretend to be prometheus, or do i need to do that separately also, how long does e.g. Jaeger keep traces around? are they created on-demand, or built up from some sort of in-memory thing, or... whatever basically i'm a little confused about the practical difference between logs vs metrics vs spans/tags vs traces keep in mind i don't really know what i'm talking about animist fucked around with this message at 03:41 on Apr 30, 2019 |
#
¿
Apr 30, 2019 03:36
|
|
|
|
| # ¿ May 14, 2024 13:40 |
|
|
yard salad posted:lol we just replaced our JMS-driven event bus with a kafka/zoopkeeper solution. the entire enterprise publisher/subscription config process is still an email to the one guy who knows how it works. you send a message and eventually you get a response. sounds like any other distributed system to me imo
|
|
#
¿
May 25, 2019 22:32
|
|
|
just use grep
|
|
#
¿
Jun 16, 2019 15:29
|
|
|
is there a good way to identify bottlenecks in a bunch of short-lived cloud spot instances? prometheus has pushgateway which seems ok but i haven't tried to actually set it up yet
|
|
#
¿
Jul 9, 2019 07:24
|
|
|
CRIP EATIN BREAD posted:you want tracing, not just metrics. hm, yeah probably. well i don't need anything right away anyway
|
|
#
¿
Jul 10, 2019 06:59
|
|
|
its because you've lived a life of sin
|
|
#
¿
Jul 12, 2019 00:23
|
|
|
|
| # ¿ May 14, 2024 13:40 |
|
|
motedek posted:a recruiter told swim datadog is creating a special task force to reduce cloud spend lmbo  poo poo guys what are we gonna do with all this data
|
|
#
¿
Jul 28, 2020 23:49
|
|