Felix Barnsteiner
Felix Barnsteiner
I agree. This seems to be a gap in the spec for https://github.com/elastic/apm/blob/main/specs/agents/handling-huge-traces/tracing-spans-dropped-stats.md.
Which are the URLs you'd like to capture the request body for? We could either add them to the static list of URLs where agents capture the body or add...
> Question: what remaining benefits are there to including transaction.id in span documents, or in transaction documents for that matter? For log correlation, it can be useful to just inject...
> IIANM, you could switch the Java agent's log correlation code to inject span.id for just the transaction's ID. i.e. just change this constant: It might be confusing to correlate...
If there's no icon for a given type/subtype, I think there should be a fallback to show either only the `subtype` or `type.subtype` in a badge.
The problem is that there might already be spans created and reported for this transaction. Should we disallow ignoring a transaction if there is already a span for it? We...
One issue I see is that if there has already been an external span which propagated the trace context, then the resulting transaction is orphaned as well. But that's probably...
I agree this is a confusing name. The problem is that it has to be aligned with the other Elastic APM agents. But that doesn't mean we can't change it...
I have also found this very confusing +1 to switch the semantics of 0 and -1
SGTM. Any volunteers to draft a spec?