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.111.0:
- Do not instrument npm or yarn when started via @instana/collector/src/immediate (instead, only instrument the child process started by npm start or yarn start).
- Do not instrument npm or yarn on AWS Fargate (instead, only instrument the child process started by npm start or yarn start).
- Do not instrument npm or yarn on Google Cloud Run (instead, only instrument the child process started by npm start or yarn start).
Changelog
1.110.5:
- Depend on exact versions of
@instanapackages, not a version range. This makes sure all@instanapackages are updated in sync and it avoids internal packages likecorebeing updated while consuming packages likecollectorstay on an older version.
Changelog
1.110.4
- Bring back core/util polyfill for Buffer.fromString for backwards compatibility.
Changelog
1.110.3
- Exponential backoff retry strategy for failed announce attempts. This helps with agents that have not yet attached to the container (and thereby not seen the process) and thus will reject the very first announce attempt.
- Remove polyfill for Buffer.fromString (for Node.js versions up to 4.5 which we no longer support).
Changelog
1.110.2
- Improve support for pino log calls that only receive a merging object argument.
Changelog
1.110.1
- Fix Node.js 6 compatibility by downgrading
tardependency of@instana/shared-metricsfromtar@6totar@5.
Changelog
1.109.0
- Improve user experience around native add-on dependencies of
@instana/collector:- Add precompiled archives for some combination of OS, architecture, libc-flavour and ABI-version.
- Try to use the precompiled native add-on if loading a native add-on fails initially.
- Try to rebuild the native add-on on demand as a fallback.
Changelog
1.108.0
-
Implement batching for very short (< 10 ms), high-frequency database spans (opt-in in this release, will be switched to default behaviour in one of the next releases). To enabled it right now, any of the three following methods can be used:
-
Set the environment variable
INSTANA_SPANBATCHING_ENABLED=true. -
Use in-code configuration:
config.tracing.spanBatchingEnabled: true. -
Add this to the agent's
configuration.yaml:com.instana.plugin.nodejs: span-batching-enabled: true
-
-
[AWS Lambda] Check type of Lambda error messages and stringify if necessary.