fix(instrumentation-pg): ensure db.client.operation.duration metric is recorded for Promises API usage of pg #2480
Conversation
…s recorded for Promises API usage of pg Refs: open-telemetry#2380
| @@ -277,6 +277,7 @@ describe('pg-pool', () => { | |||
| await client.query('SELECT NOW()'); | |||
| } finally { | |||
| client.release(); | |||
| await newPool.end(); | |||
There was a problem hiding this comment.
reviewer note: This is an unrelated change. It fixes a few-second hang in the test file completing (presumably on a pool connection timeout).
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2480 +/- ##
==========================================
- Coverage 90.74% 90.73% -0.02%
==========================================
Files 156 156
Lines 7723 7725 +2
Branches 1588 1588
==========================================
+ Hits 7008 7009 +1
- Misses 715 716 +1
|
|
The codecov issue is that the |
| const metrics = resourceMetrics.scopeMetrics[0].metrics; | ||
| assert.strictEqual( | ||
| metrics[0].descriptor.name, | ||
| 'db.client.operation.duration' |
There was a problem hiding this comment.
nit: can you use the variable here?
I made a similar update on https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2475/files#diff-682483846290c7e14fba934e5f5effaaa2ff8e84e94f511300af6d0120a59251R53
|
That was an awesome catch! Thanks for finding and fixing it! |
Refs: #2380
While working on pg tests in #2464 I accidentally noticed that the duration metric added to instr-pg in #2380 didn't work if the Promises API of the pg client was used.