Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create postgres.js #139

Closed
wants to merge 1 commit into from
Closed

Create postgres.js #139

wants to merge 1 commit into from

Conversation

brianc
Copy link

@brianc brianc commented Apr 23, 2014

Placeholder file to begin discussion/work for adding node-postgres instrumentation.

Placeholder file to begin discussion around adding instrumentation for node-postgres
@brianc
Copy link
Author

brianc commented Apr 23, 2014

I'm happy to help out on this any way I can. 😄

@cdnbacon
Copy link

cdnbacon commented May 2, 2014

Woohoo! Happy to lend a hand as well. Was just poking around to see how the MySQL version was implemented. I'd love to see this happen (or make it happen), since I've been spoiled with seeing traces for Ruby+PG in new relic, and now my traces for Node leave me wanting more...

@groundwater do we just need to get inspired by https://github.com/newrelic/node-newrelic/blob/master/lib/instrumentation/mysql.js, or is there more secret sauce necessary?

@groundwater
Copy link
Contributor

@cdnbacon yes, if you want to take a stab at it, the mysql.js instrumentation file is a great place to start looking.

The key thing to know is that our out transaction tracer uses the continuation-local-storage module to pass state between async requests. Connection pooling causes state to get lost, so you'll need to use .bind from the CLS module. If it gets hairy @wraithan and I can definitely help you out along the way.

This is also on our roadmap, but not immediately.

Thank you for the help!

@cdnbacon
Copy link

cdnbacon commented May 2, 2014

@groundwater is there a vagrant box or docker image we can use to test? I was looking through the contributing guidelines and it seems there are quite a few services to kick off to get them running...

@groundwater
Copy link
Contributor

@cdnbacon that's a totally reasonable request, but unfortunately not yet. You don't need any services running, the tests take care of that themselves. You just need the executable on your PATH.

I won't be merging with the big green button in any case, so if you break something else it's not the end of the world. Best effort works for me 👍

@wraithan
Copy link
Contributor

wraithan commented May 2, 2014

A thing to note is that the file needs to be named the same as the module name. So it will be need to be pg.js. Aside from that mysql.js will be a decent starting point, feel free to ping me on here or on irc.freenode.net with any questions you have.

@jwhitehorn
Copy link

👍 This is literally the only thing keeping me from upgrading my New Relic subscription.

jsumners-nr pushed a commit to jsumners-nr/node-newrelic that referenced this pull request Apr 16, 2024
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 19, 2024
…/moment-2.29.4

Bump moment from 2.29.2 to 2.29.4
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 23, 2024
…/moment-2.29.4

Bump moment from 2.29.2 to 2.29.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants