Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
Socket
Sign inDemoInstall
Socket
Sign inDemoInstall

@instana/autoprofile

Package Overview
Dependencies
Maintainers
0
Versions
182
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@instana/autoprofile - npm Package Versions

1
…
…
19

1.108.0

Diff
basti1302
 published 1.108.0 •

Changelog

Source

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.

1.107.0

Diff
basti1302
 published 1.107.0 •

Changelog

Source

1.107.0

  • Add instrumentation for @google-cloud/pubsub.

1.106.6

Diff
basti1302
 published 1.106.6 •

Changelog

Source

1.106.6

  • Fix (Elasticsearch): Adapt instrumentation for @elastic/elasticsearch for refactoring of api submodule introduced in @elastic/elasticsearch@7.9.1. (Fixes TypeError: Cannot set property 'Symbol(configuration error)' of undefined.) Also, remove obsolete stats annotation for elasticsearch spans.
  • Remove longer span reporting interval for serverless tracers, use standard interval instead.

1.106.5

Diff
basti1302
 published 1.106.5 •

Changelog

Source

1.106.5

  • [Google Cloud Run]: Minor changes for the upcoming Google Cloud Run support. Requires at least Instana back end version 189.

1.106.4

Diff
basti1302
 published 1.106.4 •

Changelog

Source

1.106.4

  • Remove direct node-fetch dependency from @instana/aws-fargate as well as @instana/google-cloud-run and move it to @instana/metrics-util instead.
  • Optimization: Only set span.data.service on first span.
  • Send span.crid/span.crtp instead of span.data.correlationId/span.data.correlationType.

1.106.3

Diff
basti1302
 published 1.106.3 •

Changelog

Source

1.106.3

  • Fix: Move event-loop-lag from optionalDependencies to dependencies, so installations with --ignore-optional will work correctly. (#258, thanks to @ThisIsMissEm).
  • [AWS Fargate]: Update dependency node-fetch version 2.6.1 (fixes https://www.npmjs.com/advisories/1556).

1.106.2

Diff
basti1302
 published 1.106.2 •

Changelog

Source

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: 0 downstream with AMQP headers.

1.106.1

Diff
basti1302
 published 1.106.1 •

Changelog

Source

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-run supports 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.

1.106.0

Diff
basti1302
 published 1.106.0 •

Changelog

Source

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_HEADERS variable.
  • 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_HEADERS also apply to HTTP exits.
  • [AWS Lambda] Improve handling for event.multiValueHeaders.

1.105.1

Diff
basti1302
 published 1.105.1 •

Changelog

Source

1.105.1

  • Fall back to process.mainModule.filename as the Node.js app's name when the package.json file is not present.
  • Capture dependencies of an app even if the package.json file is not present, by inspecting the node_modules folder that is closest to process.mainModule in the file system.
1
…
…
19
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

About

Packages

npm

Go

Maven

PyPI

Rubygems

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc