Log of significant changes, especially those affecting the supported API.
- 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
TracerOptions
interface. - Updates
thrift
package to address a security vulnerability.
- Fixes a bug where certain tracer tags were not set when using
proto
transport. - Adds TypeScript definitions for LightStep tracer specific options/methods
- Fixes a crash when
proto
transport 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
proto
transport option around the report of LightStep-specific tags. - Addresses an issue with
proto
transport 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
proto
transport option around span duration and span ids. - We now support a custom logger function (thanks @Rowno), see README for more details.
- Update
thrift
to0.11.0
. This breaks support for node.js versions <= 5.8.
- Add new option to Tracer:
disable_clock_skew_correction
bool
optional, defaults to 'false', which disables client-side clock kew correction.
- Add new option to Tracer:
transport
string
optional, 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_path
string
optional, which is an optional custom collector base path (if served behind a reverse proxy)
options
function now only logs warnings when it sees a key name it doesn't know. Previously, it threw an error.
instrument_page_load
option now defaults to false.- If
xhr_instrumentation
is 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 lightstepTracer
instance - API CHANGE:
lightstep-browser.min.js
andlightstep-browser.js
use alightstep
rather thanLightStep
prefix for LightStep symbols - API CHANGE: two new length limits for key-value logs:
log_field_key_hard_limit
andlog_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=1
will now throttle the error logging to the first error per minute - Option
delay_initial_report_millis
will 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
parent
option - 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
SpanContext
and changes frominject/join
toinject/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:
verbosity
level semantics updated2
: echo all errors (but not warnings and info statements)3
: echo all errors, warnings, and info statements>3
: same as3
but will increasing level of detail
- Add non-standard option
report_timeout_millis
- Add non-standard option
default_span_tags
- API CHANGE: Option
verbose
renamed toverbosity
0
: 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
debug
is 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_console
will no longer echo internal errors, warnings, and info logs - Adds
CHANGELOG.md