You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would love to use the zipkin-instrumentation-postgres package for tracing our Postgres calls. However, we are using an ORM which is called sequelize. This wraps the client, so the client is not available to be wrapped by the zipkin Postgres package. How would one do this? I have found an issue which kind of explains what I'm trying to do: #227. It seems like sequelizecan use CLS, although I'm unsure for what reason. I guess only for passing the transaction around without manually doing it.
Do you know any way to make this work without writing our own zipkin instrumentation for sequelize?
The text was updated successfully, but these errors were encountered:
Hi @saasen I had a look at the documentation (not an expert tho) and it seems the best option is to use https://sequelize.org/master/manual/hooks.html by wrapping the instance?. Are you up to take a shot on this with a PR? I can help with the review.
We would love to use the
zipkin-instrumentation-postgres
package for tracing our Postgres calls. However, we are using an ORM which is calledsequelize
. This wraps the client, so the client is not available to be wrapped by the zipkin Postgres package. How would one do this? I have found an issue which kind of explains what I'm trying to do: #227. It seems likesequelize
can use CLS, although I'm unsure for what reason. I guess only for passing the transaction around without manually doing it.Do you know any way to make this work without writing our own zipkin instrumentation for
sequelize
?The text was updated successfully, but these errors were encountered: