Generate spans for org.postgresql.copy.CopyManager

[OrangeDog]

You can add them with trace_methods, but that doesn't capture the SQL query for the span.name and context.db.statement.

[felixbarny (Felix Barnsteiner)]

Hi and thanks for your question

So you basically need an option to capture parameters for the trace_methods config? We have an issue for that: https://github.com/elastic/apm-agent-java/issues/427. Feel free to upvote that which helps us prioritizing it.

Note that this would probably not add the query to context.db.statement but rather something like context.arguments.0, for example.

Or do you propose we should have dedicated support for org.postgresql.copy.CopyManager? I'm not really familiar with that class. Out of curiosity: what do you use it for and why don't you use the regular javax.sql.Statement API?

Cheers,
Felix

[OrangeDog]

I was proposing dedicated support, to match the other DB spans and allow you to deal with the call nesting (e.g. copyTo(*,*) calls copyTo(*,*,*) and both get a span created when using trace_methods).

That class is necessary in order to use COPY ... STDIN/STDOUT statements, because the JDBC API only supports attaching streams to individual fields, not the whole statement.