This repository has been archived by the owner on Jun 16, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27
Deployment Tracker Service status
Patrick Titzler edited this page Dec 7, 2017
·
20 revisions
November 20, 2017: The Deployment Tracker Service is deprecated. If you are currently utilizing this service to track deployments of your sample application to the IBM Cloud you will need to migrate by the end of the year. Contact us in the advo-metrics Slack channel in IBM Watson Cloud Platform or IBM Watson Data Platform. Thank you.
- The server now responds to tracking requests with HTTP status code
410.
December 5, 2017:
- The Deployment Tracker Service no longer captures tracking requests.
- Applications that are using one of the Deployment Tracker Client libraries are advised to migrate to the Metrics Collector Service.
- The latest (and final) version of the Deployment Tracker client for Node.js on NPMJS no longer submits tracking requests. The new metrics client for Node.js can be found here.
- The latest (and final) version of the Deployment Tracker client for Python on PyPi no longer submits tracking requests. The new metrics client for Python can be found here.
December 6, 2017:
- The latest (and final) version of the Deployment Tracker client for Java on the Central Repository no longer submits tracking requests. The new metrics client for Java can be found here. Migration instructions
- The latest (and final) version of the Deployment Tracker client for Swift no longer submits tracking requests. The new metrics client for Swift can be found here.
- The latest (and final) version of the Deployment Tracker client for Electron no longer submits tracking requests.
- The latest (and final) version of the Deployment Tracker client for Go no longer submits tracking requests.
Upcoming changes:
- January 2018: The Deployment Tracker Service will switched over to idle mode. All API requests are denied and statistics pages are disabled.