How to log the actual SQL queries in ActiveRecord?

[edzhelyov]

Hey,

I'm used to seeing the actual SQL query in traces like SELECT $1, $2 FROM users, but I don't see any option to do that in OpenTelemetry. Could you explain why?

[arielvalentin]

The primary reason is that we instrument db driver spans.

The driver spans are considered DB client spans whereas we treat active record spans as higher level internal spans.

We prefer to adhere to semantic conventions, which means we target the client span for database attributes as opposed to higher level ORM spans (AR, Sequel, ROM, etc...).

[edzhelyov]

Thank you. This is my 3rd attempt to integrate OTel into a project and this time I'm able to send traces to a Jaeger backend. But to be honest it is very difficult to understand how to configure instrumentation and how to match the behavior I'm used to see from tools like NewRelic and similar.

Is there a starting point for new comers to start from and where I can contribute with documentation?

[arielvalentin]

I'd recommend contacting NewRelic customer support to ask them to update vendor specific documentation.

Cc: @kaylareopelle @hannahramadan @jack-berg

[kaylareopelle]

Hi @edzhelyov! New Relic's Ruby agent doesn't instrument the lower-level client libraries and instead reports SQL at the ORM-level using Active Record/Sequel, etc. Since OpenTelemetry instruments the client gems (mysql2, trilogy, pg), this may be the cause of the difference in your traces.