Package Exports
- diagnostic-channel-publishers
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (diagnostic-channel-publishers) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Diagnostic Channel Publishers
Provides a set of patches for common Node.js modules to publish instrumentation data to the diagnostic-channel channel.
Currently-supported modules
@azure/*latestredisv2.x, v3.xmysqlv2.xmongodbv2.x, v3.xpgv6.x, v7.x, v8.xpg-poolv1.x, v2.xbunyanv1.xwinstonv2.x, v3.x
Release notes
0.4.1 Aug 6, 2020
- Fix case where Azure SDK clients could be patched twice if different versions of
@azure/core-tracingare installed
0.4.0 Jun 18, 2020
- Add support for all Azure SDKs
- You must manually install
@opentelemetry/tracingto enable this automatic tracing. No additional configuration is required
- You must manually install
0.3.5 June 8, 2020
- Add support for
redis@3.xandpg@8.x
0.3.3 - August 15, 2019
- Fix patching issue with new mongodb@3.3.0+ driver
0.3.2 - May 13, 2019
- Fix issue with colorized Winston logging levels
- Support new Winston child loggers (
winston@3.2.0+)
0.3.1 - April 22, 2019
- Changed semver for mysql patching to
mysql@2.x
0.3.0 - February 19th, 2019
- Added patching for
pg@7.x,pg-pool@2.x - Added patching for
mysql@2.16.x - Added patching for
winston@3.x - Added patching for
mongodb@3.x
0.2.0 - August 18th, 2017
- Added patching for
pg,pg-pool, andwinstonmodules - Updated build output to use
dist/folder instead of.dist/(fixes #256)