NPM LIBRARY
@risingstack/trace
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 192
- Latest version activity
- 3.18.0
- Latest registry signal
- Published
- Last synchronized
- 25 Sep 2026
Authoritative registry
Version entries link to the official registry catalogue event that supplied the record.
Open package on npm ↗Lifecycle interpretation
Publication or deletion in a package registry is a distribution signal, not a promise of maintenance or security support. Any verified publisher EOL boundary remains in the main lifecycle catalogue.
Package-version activity
Newest official registry events first.
| Version | Registry event | Signal | Release notes | Evidence |
|---|---|---|---|---|
| 2.11.0 | 9 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.10.2 | 4 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.10.1 | 4 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.10.0 | 2 May 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.9.0 | 30 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.8.1 | 29 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.8.0 | 27 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.7.2 | 26 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.7.1 | 26 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.7.0 | 26 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.6.1 | 25 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.6.0 | 22 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.7 | 20 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.6 | 18 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.5 | 15 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.4 | 13 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.3 | 13 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.2 | 11 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.1 | 8 Apr 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.5.0 | 21 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.4.4 | 10 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.4.3 | 10 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.4.2 | 3 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.4.1 | 2 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.4.0 | 1 Mar 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.3.3 | 29 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.3.2 | 25 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.3.1 | 24 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.3.0 | 22 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.2.3 | 20 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.2.2 | 19 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.2.1 | 19 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.2.0 | 16 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.1.4 | 15 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.1.3 | 10 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.1.2 | 9 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.1.1 | 7 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.1.0 | 7 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.0.1 | 3 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.0.0 | 2 Feb 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 2.0.0-beta10 | 26 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta9 | 25 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta8 | 25 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta7 | 24 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta6 | 24 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta5 | 23 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta4 | 23 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta3 | 22 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta2 | 22 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 2.0.0-beta1 | 22 Jan 2016 | PUBLISHED | Not checked yet | Official event ↗ |
| 1.13.2 | 19 Jan 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.13.1 | 13 Jan 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.13.0 | 13 Jan 2016 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.12.2 | 23 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.12.1 | 18 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.12.0 | 18 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.11.3 | 9 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.11.2 | 7 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.11.1 | 2 Nov 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.11.0 | 25 Oct 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.10.2 | 20 Oct 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.10.1 | 10 Oct 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.10.0 | 7 Oct 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.9.2 | 2 Oct 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.9.1 | 30 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.9.0 | 27 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.8.0 | 21 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.6 | 18 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.5 | 14 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.4 | 10 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.3 | 4 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.2 | 4 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.1 | 3 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.7.0 | 2 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.6.2 | 1 Sep 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.6.1 | 27 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.6.0 | 26 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.5.1 | 19 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.5.0 | 12 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.4.0 | 7 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.3.0 | 6 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.2.0 | 6 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.7 | 5 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.6 | 4 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.5 | 2 Aug 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.4 | 31 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.3 | 29 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.2 | 27 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.1 | 26 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.1.0 | 25 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.0.1 | 22 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |
| 1.0.0 | 22 Jul 2015 | DEPRECATEDversions less than 3.1.0 use an obsolete API for reporting transaction traces. This API is going to be removed, and traces will be no longer collected from this agent afterwards. Upgrade your agent as soon as possible to prevent service disruption. If you are still using 2.x, note that 3.x drops support for Node.js v0.10 | Not checked yet | Official event ↗ |