Hey @nitin.chauhan
The very design of the Amplitude platform is making sure we are intentional in our instrumentation to answer the questions which have the most impact, rather than auto-tracking every possible event which happens.
Here are some pretty good posts by Jeffrey and Adam on this very concept and why Amplitude doesn’t support in auto-tracking -
https://amplitude.com/blog/why-we-didnt-build-auto-tracking-for-amplitude
https://amplitude.com/blog/autotrack-is-bad
Hope this helps!
Thanks for the details @Saish Redkar , I understand your point on data not being useful after some time. My main concern is how Amplitude is making users self sufficient so there is no dependency on Engineering/ Deployments/ production time scenarios and more. Please let know if any other way to do it with no strings attached with engineering cycles.
You are right, the dependencies introduced can cause quite a pain in the instrumentation workflow.
I recently came across Amplitude’s Iteratively docs which try to address to some extent on how instrumentation can be more streamlined and integrated with existing engineering workflows using a git like methodology. It doesn’t completely eliminate the dependency or bring in the total self-serve aspect, but worth looking at it. Hope that helps.