Focused on improving. Results-driven ever-growing person. Professional software consultant, 15+ years of experience. Crafting software since 8. Full stack developer. OSS enthusiast.
Thanks for your reply. You made me think about my own question.
My original intent was to investigate how we developers monitor announcements like this one:
Starting January 23, 2018, we will no longer support Google Mobile Ads (GMA) SDK versions lower than 7.0.0 for Android or iOS. To continue serving mobile ads from AdMob, Ad Exchange, or DFP after this date, please upgrade to the latest Google Mobile Ads SDK
Bachelor's and Master's in CS from MIT. Previously, worked @ Microsoft & Zynga. Currently Co-Founder of Moesif (moesif.com), the most advanced API analytics platform.
Well, yes. Moesif won't capture news announcements like that.
But if say an micro service or external service is upgraded (or if team for that micro service is doing continuous integration and new version is released automatically), and errors are caused by that, moesif actually will detect and attribute it correctly.
Sometimes the error caused by upgrade of micro service can be really subtle. For example, if you have a mesh of micro services that depends on each other, error at one location could actually be caused by another micro service that seemed to function fine.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for your reply. You made me think about my own question.
My original intent was to investigate how we developers monitor announcements like this one:
Starting January 23, 2018, we will no longer support Google Mobile Ads (GMA) SDK versions lower than 7.0.0 for Android or iOS. To continue serving mobile ads from AdMob, Ad Exchange, or DFP after this date, please upgrade to the latest Google Mobile Ads SDK
This announcement was published on support.google.com/admob/release-n...
Well, yes. Moesif won't capture news announcements like that.
But if say an micro service or external service is upgraded (or if team for that micro service is doing continuous integration and new version is released automatically), and errors are caused by that, moesif actually will detect and attribute it correctly.
Sometimes the error caused by upgrade of micro service can be really subtle. For example, if you have a mesh of micro services that depends on each other, error at one location could actually be caused by another micro service that seemed to function fine.