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

Prisma connection pool utilization #1885

Open
philomory opened this issue Nov 23, 2023 · 2 comments
Open

Prisma connection pool utilization #1885

philomory opened this issue Nov 23, 2023 · 2 comments

Comments

@philomory
Copy link

Is your feature request related to a problem? Please describe.

We ran into a situation where our Prisma connection pool was running out of available connections, and it would have been nice to have that exposed via a metric we could monitor.

Feature Description

One or more Datastore metrics for Prisma datastores describing the state of the connection pool. Either a percentage utilization, separate metrics for the size of the pool and the current number of available vs in-use connections, or both.

Describe Alternatives

Prisma itself contains (preview/beta) support for exporting metrics in a Prometheus format, although getting this into New Relic is much more complicated than just having the APM agent submit the metric in question "natively"; also, as mentioned the current metrics support in Prisma itself is a preview feature.

Priority

Please help us better understand this feature request by choosing a priority from the following options:
Really Want

@workato-integration
Copy link

@coreyarnold
Copy link
Member

@philomory thanks for your suggestion! This seems like a reasonable thing for us to look into. I'll get with the team and see what how much effort this would be.

@bizob2828 bizob2828 added this to Triage Needed: Unprioritized Features in Node.js Engineering Board via automation Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Node.js Engineering Board
  
Triage Needed: Unprioritized Features
Development

No branches or pull requests

2 participants