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: allow disabling postgres, nestjs automatic instrumentation through env-var #355

Merged

Conversation

GuyMoses
Copy link
Collaborator

@GuyMoses GuyMoses commented May 1, 2024

No description provided.

@GuyMoses GuyMoses requested a review from harelmo-lumigo May 1, 2024 16:43
});

let lumigoPgInstrumentation = new LumigoPgInstrumentation();

test('disable pg instrumentation', () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd go further and replace this with an actual instrumentation test, that sets the env-var to false and makes sure no spans were produced - see an example of something similar I've done with the aws-sdk V3 .

@GuyMoses GuyMoses changed the title feat: allow disabling pg automatic instrumentation through env-var feat: allow disabling postgres, nestjs automatic instrumentation through env-var May 15, 2024
@GuyMoses GuyMoses merged commit b4d505f into main May 16, 2024
80 of 89 checks passed
@GuyMoses GuyMoses deleted the RD-12662-allow-disabling-postgres-instrumentation-on-js-distro branch May 16, 2024 07:09
lumigo-circleci-github-user pushed a commit that referenced this pull request May 16, 2024
# [1.41.0](v1.40.1...v1.41.0) (2024-05-16)

### Features

* allow disabling postgres, nestjs automatic instrumentation through env-var ([#355](#355)) ([b4d505f](b4d505f))
@doriaviram
Copy link
Contributor

🎉 This PR is included in version 1.41.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants