This message was deleted.
# puppet-enterprise
s
This message was deleted.
s
I don’t know the state of that TBH, but as for inclusion in the console… what I really want to do for things like that is leverage tasks and plans with custom output templates for extensions like that. We can’t build everything into the console, but if we can expand the ways users can add things in a supported way then we’re golden
b
ah sounds nice
s
that’s a longer term project though
c
OpenTelemetry instrumentation for PE services is probably the best thing to focus on. With that, flamegraphs are a matter of shipping the traces to Tempo, Jaeger, Zipkin, or a commercial APM product.
Because the log-scraping solution in that KB article is a very, very poor way of doing it. It's banging rocks together compared to what can be done with the tooling developed in the past 5 years.
b
I totally agree and I think I even raised a ticket for opentelemetry support some time ago. Do you know if there is currently anybody working on it / is that on any roadmap?
c
It has been looked into from time to time, but there's nothing prioritized that I know of.
b
Do you know if it helps when PE customers request it?
Or: If that isnt on the roadmap, what is on the roadmap?
c
It definitely helps. Tracing, Metrics, and other Observability improvements have to fight extra hard against other features because they are often not requested. You only miss them when things are not working quite right and it also requires a good deal of meta-awareness to realize that a performance problem is difficult because of insufficient observability.
b
yeah. You only notice the lack of tracing/metrics when you have a huge problem
and then its a point where you think "now it would be helpful to have 6 months of metric history to see when something changed"
on a positive side, the puppet_operational_dashboard really really helps
d
@Marty Ewings++ ^^
m
🙂