chore(deps): update dependency zipkin to v0.22.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
zipkin	0.10.1 -> 0.22.0

---

Release Notes

openzipkin/zipkin-js

v0.22.0: Version 0.22.0

Compare Source

This release includes in #​476, a long requested feature (see #​201, #​135, #​124, #​175 and #​106) but we did not want to release it until we got users involved in the testing of the feature with real use cases. Thanks @​kurtharriger for taking care of the unit testing part and @​mikhailrojo for actually testing the feature in production code.

We also include some fixes:

• fix(http-reporter): add fallback for fetch (#​497) by @​rafael-anachoreta
• chore: eps correctness (#​505) by @​mikhailrojo

v0.21.0: Version 0.21.0

Compare Source

This version mainly adds support for AWS SQS transport, thanks to @​asanluis (for the code, iterations and spirit) but also drops support to node8 on builds as EOL.

v0.20.0: Versión 0.20.0

Compare Source

• Adds support for configurable fetch API (#​485) - thanks to @​petermetz
• Fix readme for empty module (#​489) - thanks to @​chrunchyjesus

v0.19.2

Compare Source

v0.19.1: Version 0.19.1

Compare Source

[#​439] Added agent option to http transport - thanks to @​RAWeber
[#​449] Fixes the express instrumentation by using right hooks in the response reported by @​jeffthompson1971 in https://github.com/openzipkin/zipkin-js/pull/417#issuecomment-540147193

v0.19.0: Version 0.19.0

Compare Source

This version includes the brand new zipkin-instrumentation-koa package by @​shumsky, some gaps filled in the Typescript interface by @​Igor-lkm (https://github.com/openzipkin/zipkin-js/pull/426 and https://github.com/openzipkin/zipkin-js/pull/428) and a complete refactor of the test suite for instrumentations.

v0.18.6: Version 0.18.6

Compare Source

This adds the ability to manually flush spans from the BatchRecorder and fixes a couple bugs, most notably Error: Must be valid TraceId instance. Thanks for all the feedback and help making things better!

• @​jcchavezs added BatchRecorder.flush() for manual control of span reporting (ex in lambda) #​362
• Fixes Error: Must be valid TraceId instance relating to transpilation #​422
• Fixes wrong Span.kind on ServerRecv and dropped ClientAddr annotations #​418

v0.18.5

Compare Source

v0.18.4: Version 0.18.4

Compare Source

Major improvements in span reporting and debugging support. Notably the issue described in https://github.com/openzipkin/zipkin-js/issues/365 was addressed in https://github.com/openzipkin/zipkin-js/pull/383 with tones of tests in https://github.com/openzipkin/zipkin-js/pull/378, https://github.com/openzipkin/zipkin-js/pull/376, https://github.com/openzipkin/zipkin-js/pull/372, https://github.com/openzipkin/zipkin-js/pull/369, https://github.com/openzipkin/zipkin-js/pull/380 and https://github.com/openzipkin/zipkin-js/pull/385. All these great work is thanks to @​adriancole

v0.18.3

Compare Source

v0.18.2

Compare Source

v0.18.1

Compare Source

v0.18.0: Version 0.18.0

Compare Source

• [#​352][instrumentation-grpc-client] Fixes trace identifiers not being not correctly cleaned up after setting them in the grpc interceptor. Thanks to @​high-stakes
• [#​355][instrumentation-request] Fixes mutation in the context in httpclient.recordResponse. Thanks to @​chris-smith-zocdoc
• [#​357][instrumentation-kafkajs] Adds instrumentation for kafkajs. Thanks to @​high-stakes

v0.17.1: Version 0.17.1

Compare Source

This release includes some fixes and upgrades. Notably we include a GOT http instrumentation.

• [#​157] Adds GOT instrumentation, thanks to @​juhovh
• [#​327] httpServer instrumentation should let sampler to make decision if missing sampled header, thanks to @​kenspirit
• [#​185] hapi 17 support, thanks to @​akiellor and @​PaulinaStypinska

We also dropped support for node 6 as it is becoming unsupported this month.

v0.16.2: Version 0.16.2

Compare Source

This patch version includes a fix for #​330 thanks to @​ghermeto.

v0.16.1: Version 0.16.1

Compare Source

This patch version includes a couple of fixes:

• [#​329] Fix fetch signature. Thanks to @​FredrikAppelros
• [#​331] Fix the browser bundle. Thanks to @​BenoitZugmeyer

v0.16.0: Version 0.16.0

Compare Source

• [#​311] Makes browser support a first class citizen. Thanks to @​ewhauser
• [#​318] Allows the traceId to be accessed from sequential promises in the route handler. Thanks to @​ghermeto
• [#​320] Adds http.route as span name. Thanks to @​ghermeto
• Removes payload recording in batched commands. Thanks to @​voldern
• Fixes the installation of zipkin-instrumentation-grpc-client. Thanks to @​li8
• Upgraded the node-fetch version to 2.3.0 in zipkin-transport-http. Thanks to @​Kiho

v0.15.0: Version 0.15.0

Compare Source

This astonishing release comes with many new features and improvements.

• Upgraded babel dependencies to babel 7 - thanks @​DavideCarvalho
• Improved Option type - thanks to @​briancavalier
• Dropped node 4 from CI (as it was never intended to be supported) - thanks to @​DavideCarvalho
• Added configurable logging module as argument - thanks to @​ghermeto
• Added superagent instrumentation - thanks to @​ghermeto
• Added timestamp parameter to recordAnnotation - thanks to @​haoguanjun
• Performance improvements for restify middleware - thanks to @​ghermeto
• Added support for maxPayloadSize option in HttpLogger - thanks to @​juhovh
• Added supportsJoin in HttpServer middleware - thanks to @​juhovh
• Added instrumentation for connect (works for both express and restify) - thanks to @​ghermeto
• Added GRPC client instrumentation - thanks to @​ghermeto
• Added support for restify 7+ - thanks to @​ghermeto
• Added support for default tags in tracer - thanks to @​ghermeto

More so, many dramatic improvements to typescript code thanks to @​DavideCarvalho and thanks to @​sonybinhle for the code reviews.

v0.14.3: Version 0.14.3

Compare Source

This release includes two fixes:

1. [#​248][#​190][#​268][#​263] Fixes TS signatures and types to be consistent with the JS implementations. Thanks to @​sonybinhle
2. [#​195] Fixes warnings with create-react-app. Thanks to @​DavideCarvalho

v0.14.2: Version 0.14.2

Compare Source

This new release include the brand new package zipkin-instrumentation-request-promise which adds tracing to the request and request-promise libraries. Thanks to @​mkante for this effort.

It also improves the tests for client/server instrumentation by adding errors based on the status code.

Finally, thanks to @​jnazander, there is a troubleshooting section for zipkin-instrumentation-cls.

v0.14.1: Zipkin JS 0.14.1

Compare Source

https://github.com/openzipkin/zipkin-js/pull/254 Fix TS compilation error for missing Option type argument - @​kevin-greene-ck

v0.14.0: Zipkin JS 0.14.0

Compare Source

Zipkin JS adds support for Sampling Flags and some other important improvements to the library:

• https://github.com/openzipkin/zipkin-js/issues/197 Sampling Flags allows a user to force a trace with a sampling decision. This could be useful for example when you want to debug all requests from an specific host or all traces for requests from an specific IP. In both cases, passing the X-B3-Flags: 1 or X-B3-Sampled: 1 will force downstream to respect those decisions.
• https://github.com/openzipkin/zipkin-js/issues/217 replaces http.url in favor of http.path in server tracing. This improvement trims the query string parameters coming from upstream to avoid the collection of sensitive information like api keys or e-mails in the query string. Thanks to @​pchiwan.
• https://github.com/openzipkin/zipkin-js/pull/246 fixes the signature of the ConsoleRecorder constructor as it does not match ts type. Thanks to @​tomasAlabes.
• https://github.com/openzipkin/zipkin-js/issues/210 records an error if there was one in the express middleware for more meaningful traces. Thanks to @​chris-smith-zocdoc
• https://github.com/openzipkin/zipkin-js/issues/236 allow httpServer instrumentation host to be overridden as httpServer instrumentation implementation was querying the OS to find the host's ip address on every request. This can lead to a performance problem when the server is under heavy load. Thanks to @​rcoedo
• https://github.com/openzipkin/zipkin-js/issues/243 ensures tag and annotation values are casted to strings according to the Zipkin v2 JSON swagger spec. Thanks to @​keitwb

v0.13.0

Compare Source

v0.12.0

Compare Source

v0.11.2

Compare Source

v0.11.1: zipkin-js v0.11

Compare Source

zipkin-js v0.11 adds PostgreSQL, TypeScript, http customization and local tracing apis.

We're quite lucky to have a community producing works like this. Don't forget to watch our repo for change you're interested in!

PostgreSQL

Those familiar with Zipkin change culture know that we aim for high quality implementations that are desired by multiple parties (rule-of-three). Thanks to @​voldern, we now have client instrumentation for postgreql and thanks to our community speaking up in favor, it is merged!

Here's a snippet from the README:

const client = new ZipkinPostgres.Client(connectionOptions);
const pool = new ZipkinPostgres.Pool(connectionOptions);

// Your application code here
client.query('SELECT NOW()', (err, result) => {
  console.log(err, result);
});

pool.query('SELECT NOW()')
  .then(console.log)
  .catch(console.error);

TypeScript

TypeScript is quickly catching fire in our repository. Many thanks to @​yonran and @​pbadenski for fleshing out declaration files, covering our base api, all transports and a couple instrumentation packages. Keep an eye out or roll up your sleeves to help complete the job!

Http transport customizations

Some folks proxy zipkin, adding aspects such as oauth they might need. Thanks to @​voldern, you can now customize headers used to transport spans, such as adding authorization.

const recorder = new BatchRecorder({
  logger: new HttpLogger({
    endpoint: 'http://your_host:9411/api/v2/spans',
    jsonEncoder: JSON_V2,
    headers: {'Authorization': 'secret'} // optional custom HTTP headers
  })
});

Local tracing

Local tracing is capturing activity that starts before remote service calls, or in-between them. This can be used to label code in a client, such as react-native, or a notable operation you need to pay attention to for SLA reasons. Thanks to a lot of help from @​eirslett @​DanielMSchmidt and @​sundarsy, we now have a new api command Tracer.local which wraps synchronous or promise results.

Here's an example tracing a synchronous function:

// A span representing checkout completes before result is returned
const result = tracer.local('checkout', () => {
  return someComputation();
});

Here's an example tracing a function that returns a promise:

// A span is in progress and completes when the promise is resolved.
const result = tracer.local('checkout', () => {
  return createAPromise();
});

Look at our README or our example node or React Native projects for local tracing in action!

v0.11.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[coveralls]

Coverage remained the same at 100.0% when pulling 44b9daa on renovate/zipkin-0.x into f601099 on master.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.