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

feat(otel-node): instr-tedious #144

Merged
merged 11 commits into from
Apr 24, 2024
Merged

feat(otel-node): instr-tedious #144

merged 11 commits into from
Apr 24, 2024

Conversation

david-luna
Copy link
Member

Closes: #34

@david-luna david-luna requested a review from trentm April 23, 2024 11:03
Copy link
Member

@trentm trentm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some nits.

packages/opentelemetry-node/test/fixtures/use-tedious.js Outdated Show resolved Hide resolved
// tedious@11 and later depend on @azure/identity v1 or v2. As of
// @azure/core-rest-pipeline@1.15.0 (a dep of @azure/identity), support for
// Node.js <16 has been broken.
node: '>=16',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A thing to possibly watch out for here is this that we have in apm-agent-nodejs testing:

if (
  (semver.gte(tediousVer, '17.0.0') && semver.lt(process.version, '18.0.0')) ||
  // tedious@11 and later depend on @azure/identity v1 or v2. As of
  // @azure/core-rest-pipeline@1.15.0 (a dep of @azure/identity), support for
  // Node.js <16 has been broken.
  (semver.gte(tediousVer, '11.0.0') && semver.lt(process.version, '16.0.0'))
) {
  console.log(
    `# SKIP tedious@${tediousVer} does not support node ${process.version}`,
  );
  process.exit();
}

At some point should we bump the tedious ver we test with to the latest? If so, then we'll need to guard with node >=18.

Ah, I see open-telemetry/opentelemetry-js-contrib#1656
We should consider helping with that.

Copy link
Member Author

@david-luna david-luna Apr 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A thing to possibly watch out for here is this that we have in apm-agent-nodejs testing:

I though about it but it felt I was anticipating things (YAGNI). I guess this will be useful for #43 so we are actually going to need it. I'll add it

We should consider helping with that.

Sure!

Comment on lines 69 to 72
image: mcr.microsoft.com/mssql/server
env:
ACCEPT_EULA: 'Y'
SA_PASSWORD: 'Very(!)Secure'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:

If so, would need to change in docker-compose.yaml and use-tedious.js below.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine for me :)

@david-luna david-luna merged commit adbdea2 into main Apr 24, 2024
11 checks passed
@david-luna david-luna deleted the dluna/instr-tedious branch April 24, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: add @opentelemetry/instrumentation-tedious instrumentation
2 participants