.setAutoCollectDependencies(false) still collects dependencies
See original GitHub issueI’ve updated the application insights package from 1.8.10 to 2.2.2
Since the update the dependencies are getting collected even when .setAutoCollectDependencies(false)
is set on setup.
Is there any other option to turn this off in newer version that I missed?
This function worked correctly before the update.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Support correlation and autocollection when servers use ...
I am already able to link browser dependency with express-nodejs request. If I use tagoverride inste ... setAutoCollectDependencies(false) .
Read more >Monitor your Node.js services and apps with Application Insights
An example is appInsights.Configuration.setAutoCollectDependencies(true) . Review the changes to the default configuration in the next section.
Read more >Application Insights for Node.js - applicationinsights - npm
Finally, start automatically collecting and sending data by ... Dependency events based on whether setAutoCollectDependencies is enabled.
Read more >How to disable for automatically collecting the service bus ...
I have tried to enable Adaptive Sampling by using below code. But still it generates excess of dependency calls. s.Configure< ...
Read more >Dotansimha-applicationinsights NPM - npm.io
Add the Application Insights Node.js SDK to your app's dependencies and package.json ... Finally, start automatically collecting and sending data by calling ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For my part, the file is completely empty ( file content : ‘{ }’ ). All properties are defined with their respective methods ( e.g. : .setAutoCollectDependencies(true) to collect dependencies automatically ) It is perhaps a different problem which is evoked initially but the result being identical (duplicate of collect) I thought that it was interesting to check and to evoke it 👍
@MatejSkrbis the question is about you using Azure SDK packages like the one you mentioned, currently Azure SDK dependencies are being tracked even if configured off, there is a pull request to fix that and will publish next release, thanks.