Log of significant changes, especially those affecting the supported API.
- Upgrade webpack (#304)
- Upgrade cacheable-request, package-json (#303)
- Upgrade http-cache-semantics (#302)
- Upgrade json5 (#301)
- Upgrade loader-utils (#299)
- Upgrade opentracing (#298)
- Upgrade thrift (#297)
- Upgrade async (#296)
- Upgrade google-protobuf (#295)
- Upgrade terser (#293)
- Omit non-sampled spans from report (#290)
- Upgrade async (#288)
- Upgrade to Babel 7 (#288)
- Upgrade various dependecies (#288)
- Substitute deprecated packages (#288)
- add Node 14 and Node 16 jobs on CI (#288)
- Drop support for Node 8 and 10 (#288)
- Add missing OpenTracing spancontext methods (#279)
- Update ws and normalize-url dependencies.
- Update to thrift v0.14.1
- Update versions of underscore, lodash, handlebars, and y18n.
- Improve performance of hexToDec by using native BigInt when available.
- Bugfix for nodejs: remove throw in fetch onError handler (#246)
- Fix misnamed configuration options.
nodejs_inclusion_patternswas renamed tonodejs_url_inclusion_patternsandnodejs_exclusion_patternswas renamed tonodejs_url_exclusion_patterns. Because of this bug, the inclusion and exclusion patterns were not being recognized by instrumentation.
- Bug fix for eslint for Microsoft Edge (#241)
- Add options for auto-instrumented urls and tracing headers (#237)
- Truncate most significant 64 bits when all 0's in B3 propagator.Inject (#238)
- Support React Native with the browser tracer (#235)
- Bug fix for propagating baggage from parent span to child span
- SpanContext is now exported to facilitate creating custom propagators
- No changes
- Require node >= v8
- New option to empty span buffer on max error streak
clear_span_buffer_consecutive_errors - Upgrade eslint
- fix for fetch plugin: 'method' was always GET
- Fix missing clock offsets over proto transport
- Fix timestamp conversion for protobuf transport
- No changes (minor bump to align with 0.25.1-no-protobuf release)
- Bug fix on
fetchinstrumentation options headers being overwritten in some cases. - Re-build dist to fix failed page load on IE11 (#207)
- Fix how the
fetchshim so that it does not overwrite user-providedResponse.headers - Add clock correction and error handling for the protobuf transport's responses
- Specify correct modules in node instrumentation docs
- Add a CONTRIBUTING.md guide
- Upgrade thrift to 0.13.0 (#198)
- Guard session storage access
- update type of collector_encryption
- Fix propagator typo
- Update typing on inclusion/exclusion patterns to match docs
- Adds DataDog header support (#187)
- Removes for..of loop to support IE11 (#189)
- Add NodeJS instrumentation and shims (#184)
- Adds B3 propagator (#177)
- Fixes an issue where reporter cookies would be set with invalid key strings.
- Completely defines the
TracerOptionsinterface. - Updates
thriftpackage to address a security vulnerability.
- Fixes a bug where certain tracer tags were not set when using
prototransport. - Adds TypeScript definitions for LightStep tracer specific options/methods
- Fixes a crash when
prototransport was used and invalid responses were received. - Adds an option to exclude cookies from tracing payloads.
- The default transport has been changed to
proto. - The tracer supports empty access tokens.
- Several bugs have been fixed with the
prototransport option around the report of LightStep-specific tags. - Addresses an issue with
prototransport usage in the browser. - Fixes bug where error objects are not converted to log objects correctly.
- Implements plugin for fetch.
- Remove deprecated chrome.loadTimes() code.
- Passing fractional timestamps to span start/finish are now properly handled.
- Several bugs were fixed with the
prototransport option around span duration and span ids. - We now support a custom logger function (thanks @Rowno), see README for more details.
- Update
thriftto0.11.0. This breaks support for node.js versions <= 5.8.
- Add new option to Tracer:
disable_clock_skew_correctionbooloptional, defaults to 'false', which disables client-side clock kew correction.
- Add new option to Tracer:
transportstringoptional, defaults to 'thrift', which controls the transport method used to send reports to LightStep. Experimental Feature - Fixes a bug when logging verbosity was greater than 4 during report flushes.
- Add new option to Tracer:
collector_pathstringoptional, which is an optional custom collector base path (if served behind a reverse proxy)
optionsfunction now only logs warnings when it sees a key name it doesn't know. Previously, it threw an error.
instrument_page_loadoption now defaults to false.- If
xhr_instrumentationis enabled, Open Tracing headers are now properly sent with every xhr request, so long as that request is to a domain that matches the whitelist url rules and also does not match any of the blacklist url rules.
- API CHANGE: use
new lightstep.Tracer(opts)to return a lightstepTracerinstance - API CHANGE:
lightstep-browser.min.jsandlightstep-browser.jsuse alightsteprather thanLightStepprefix for LightStep symbols - API CHANGE: two new length limits for key-value logs:
log_field_key_hard_limitandlog_field_value_hard_limit, both specified as a number of bytes - Many implementation changes, especially support for key-value logging per OpenTracing-javascript
0.13.*
- Update the internal, automatic tracer tags to follow the convention of using a
lightstep.*prefix
- Option
verbosity=1will now throttle the error logging to the first error per minute - Option
delay_initial_report_milliswill delay the initial report to the collector by at least some value between 0 and this value. This is useful when spawning a large number of new processes to help distribute the load at startup. Note: this is a non-standard option that is not supported by other LightStep libraries and is subject to change. - Back off on errors is more now more aggressive. The back off always uses the the reporting interval, not the clock calibration interval.
- Fixes defects where the XHR instrumentation was still using the old
parentoption - Add documentation for the non-standard option
disable_reporting_loop - Add documentation and implementation for the non-standard option
disable_report_on_exit - Fixes the examples to use the newer OpenTracing APIs
- Internal logging methods renamed (no external impact)
- Full changes
- API CHANGE: migrates to the latest OpenTracing API which introduces
SpanContextand changes frominject/jointoinject/extract. See the OpenTracing migration docs for details.
- Enable gzip compression of Node.js reports from the client by default (this is controlled by a non-standard option
gzip_json_requests)
- Fix defect in error handling of failed requests
- MINOR API CHANGE:
verbositylevel semantics updated2: echo all errors (but not warnings and info statements)3: echo all errors, warnings, and info statements>3: same as3but will increasing level of detail
- Add non-standard option
report_timeout_millis
- Add non-standard option
default_span_tags
- API CHANGE: Option
verboserenamed toverbosity0: never echo anything to the host application's console1: echo only the first error to the host application's console> 1: echo internal errors, warnings, and info statements to the host application's console. Higher values will yield more detailed logs
- API CHANGE: Option
debugis no longer valid and will generate an error if used - Internal errors, warnings, and info logs will no longer show up in the collected traces
- Option
log_to_consolewill no longer echo internal errors, warnings, and info logs - Adds
CHANGELOG.md