Skip to content
This repository has been archived by the owner on Feb 7, 2018. It is now read-only.

migrating to the new metrics tracker client

Patrick Titzler edited this page Dec 7, 2017 · 2 revisions

Overview

Why you should consider migrating ASAP

  • The existing Deployment Tracker Service no longer stores deployment tracking information that the Deployment Tracker client for Python you are using is sending.
  • Existing links to the deployment badge image and the "Deploy to IBM Cloud" image that you might have embedded in your README will be broken soon.

Disabling deployment tracking

Should you decide to not migrate to the new client, please disable deployment tracking:

  • Remove the tracking code from your application
    import cf_deployment_tracker
    ...
    cf_deployment_tracker.track()
    
  • Remove cf_deployment_tracker from requirements.txt

Migration steps

To migrate to the new tracking infrastructure:

  • Remove the tracking code from your application
    import cf_deployment_tracker
    ...
    cf_deployment_tracker.track()
    
  • Remove cf_deployment_tracker from requirements.txt
  • Follow the metrics client for Python setup instructions
  • Update your Deployment badge URLs and "Deploy to IBM Cloud" button URLs in your README.md
    • Deploy your application to IBM Cloud
    • Open https://metrics-tracker.mybluemix.net/stats and log in (access is restricted to IBM employees)
    • Locate your repository entry
    • Open the repository details page and note the new button/badge URLs
    • Update your existing README.md and other collateral with the designated URL/markdown code.

Note: The existing deployment statistics for your repository will not be migrated.