jackshirazi
jackshirazi
@tobiasstadler that's an excellent idea!
@felixbarny have the PRs referenced (https://github.com/elastic/ecs-logging-java/pull/168 and https://github.com/elastic/apm-agent-java/pull/2296) implemented what you intended for this, or is there more to do?
Excellent work! Just need to add a CHANGELOG entry (and possibly a supported tech entry) and you're done!
https://www.elastic.co/blog/create-your-own-instrumentation-with-the-java-agent-plugin > @jackshirazi this sounds like a perfect candidate for an external plugin. Once we have the blog posts to share about that, please do.
I would say any refactorings should be driven by the community, so I've closed that. The other two are still valid
I agree you can do this from existing metrics. But also agree this is a nice separate metric to have. I think it's something that could be added as a...
We already have a start timestamp in the AbstractSpan superclass, so this needs a thread which loops through all active AbstractSpan and ends them if over time. So my initial...
Hi Kotliners. It's unlikely that Elastic will put resources into this any time soon. Ideally the Kotlin community would add this into the agent. Here's some options 1. We've recently...
I think this is doable without too much effort. We already get all the GC pauses. A simple way would be for every Span/Transaction get added to a list and...
You are absolutely right, I was way overthinking it! And even if that call is not consistent, we can easily maintain our own cumulative pause counter