Original Announcement Date
|October 1st, 2019|
|December 1st, 2019|
What does this announcement mean?
Starting December 1st, 2019
- Ionic Appflow customers will no longer have access to the Ionic Monitoring service.
- This change was first announced in October. Please see the original post for details.
What happened today?
- The Monitoring service has been shut down and the UI removed for customers in the Ionic Appflow Dashboard.
- Any API calls to the Monitoring service will no longer return errors from your app; these calls will do nothing and return HTTP 201 status codes.
- In 2020, the Ionic team will entirely remove the code for the Monitoring service. At that time, you may begin to receive errors if using the old Monitoring APIs in your application.
- It is highly recommended that you remove the Monitoring service from your application as noted so that you are unaffected by this change in the future.
What do I need to do if I’m using still using the Monitoring API?
- If your Ionic application still includes the
@ionic/propackage, it is recommended to remove it from your application. If you are also using the Deploy API, make sure you are on the latest version of
cordova-plugin-ionicand update your imports and code per the documentation.
- If your application still includes references to
IonicErrorHandler, remove the associated code from your application as soon as possible
I need an alternative to Monitoring for my application(s). Can you recommend any other services?
Common alternatives to Monitoring include Sentry.io and Firebase Crashlytics. A number of our clients have reported positive experiences with Sentry in particular, which has built an entire product around error monitoring as a service. Both services come with generous free-tier offerings for smaller applications, with paid tiers after a certain amount of usage.
If you have questions or concerns, please reach out to us via email at firstname.lastname@example.org.
Article is closed for comments.