Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
instana-aws-lambda-auto-wrap
Advanced tools
instana-aws-lambda-auto-wrap - npm Package Versions
Changelog
1.106.6
- Fix (Elasticsearch): Adapt instrumentation for
@elastic/elasticsearchfor refactoring ofapisubmodule introduced in@elastic/elasticsearch@7.9.1. (FixesTypeError: Cannot set property 'Symbol(configuration error)' of undefined.) Also, remove obsoletestatsannotation forelasticsearchspans. - Remove longer span reporting interval for serverless tracers, use standard interval instead.
Changelog
1.106.5
- [Google Cloud Run]: Minor changes for the upcoming Google Cloud Run support. Requires at least Instana back end version 189.
Changelog
1.106.4
- Remove direct
node-fetchdependency from@instana/aws-fargateas well as@instana/google-cloud-runand move it to@instana/metrics-utilinstead. - Optimization: Only set
span.data.serviceon first span. - Send
span.crid/span.crtpinstead ofspan.data.correlationId/span.data.correlationType.
Changelog
1.106.2
- [AWS Fargate]: Make optional dependencies on native add-ons truely optional (do not break the Docker build on
RUN /instana/setup.sh). - Fix: Propagate
X-INSTANA-L: 0downstream with AMQP headers.
Changelog
1.106.1
- Fix bogus warning about invalid configuration emitted during startup (
"Invalid configuration: config.tracing.http.extraHttpHeadersToCapture is not an array, the value will be ignored: {}"). - [Google Cloud Run]: Experimental in-process data collection for Google Cloud Run services via the new package
@instana/google-cloud-run. Requires at least Instana back end version 185.@instana/google-cloud-runsupports Node.js 8.6.0 or later. Note that this is an early technical preview and not ready for general usage. At this time, no support can be provided for this new package. This will change once Google Cloud Run support becomes generally available with Instana.
Changelog
1.106.0
- Fix(HTTP1/Server): Also set Server-Timing header when X-INSTANA-T is incoming (that is, not only when we start a fresh trace).
- Fix(HTTP1/Server): Do not append another intid key-value pair to Server-Timing if it is already present.
- Fix(HTTP2/Server): Add support for website monitoring back end correlation via Server-Timing header.
- Fix(HTTP2/Server): Add support for X-Instana-Service.
- Fix(HTTP2/Server): Inject the trace ID into the request to enable application code to inject it into the response body.
- Fix(HTTP2/Server): Use case-insensitive header matching as incoming headers are already normalized to lower case (performance improvement).
- Add support for
INSTANA_EXTRA_HTTP_HEADERSvariable. - Fix(HTTP1/HTTP2): Fix handling for headers of type array (normalize to string, separated by 0x2C 0x20).
- [AWS Fargate] Add support for
INSTANA_ZONE. - [AWS Fargate] Add support for
INSTANA_TAGS. - Secrets Filtering: Replace values for filtered query parameters with
<redacted>instead of removing the whole key-value pair. - [AWS Fargate] Add support for
INSTANA_SECRETS. - [AWS Fargate] Add support for
INSTANA_EXTRA_HTTP_HEADERS. - [AWS Lambda] Add support for
INSTANA_SECRETS. - [AWS Lambda] Make
INSTANA_EXTRA_HTTP_HEADERSalso apply to HTTP exits. - [AWS Lambda] Improve handling for
event.multiValueHeaders.
Changelog
1.105.1
- Fall back to
process.mainModule.filenameas the Node.js app's name when thepackage.jsonfile is not present. - Capture dependencies of an app even if the
package.jsonfile is not present, by inspecting thenode_modulesfolder that is closest toprocess.mainModulein the file system.
Changelog
1.104.0
- Drop support for Node.js versions 4 (which was EOL 2018-04-30) and 5 (EOL 2016-06-30) in
@instana/collector. If you want to use@instana/collectorwith Node.js version 4 or 5 please pin@instana/collectorto version1.103.0. - Fix: Capture MongoDB aggregate operations correctly.
- Fix: Keep async context across Mongoose custom thenables.