yCrash RELEASE 0_37 NOTES -------------------------- + 'Export Summary' feature in the Ycrash application facilitates users to export reported incidents in a particular month to a CSV file. For more details refer to https://docs.ycrash.io/ycrash-features/export-summary.html + Once yc agent completes transmitting all artifacts (i.e. thread dumps, GC logs,....) to the YC server, it will print a YAML snippet in the console. This snippet contains the URLs to the dashboard report & metrics details. This feature facilitates engineers to generate alerts or build any solution based on the metrics. For more details refer https://docs.ycrash.io/ycrash-agent/agent-response.html + Whenever user is taken to error page, application is printing 'If you think this is not a valid error & need resolution, please contact team@tier1app.com'. Besides that in few other places are we are printing contact 'team@tier1app.com'. We are providing an option to replace this email address with your organization's custom email address or any team's name. For more details on how to use this feature refer to 'section 9' in https://blog.tier1app.com/2016/10/30/enterprise-edition-admin-manual/ + A New section called 'Exception' is introduced. In this section we look out for Excpetion or Error stacktraces in the thread dump. If we find them then it will be reported. For more details refer to https://blog.fastthread.io/2020/06/10/threads-throwing-exception/ + In the HeapHero report there is 'Threads' section. When user clicks on the hyperlink in this section, he will taken to fastThread analysis report. Only in this fastThread report, problems related to thread dump will be reported. Now in the 'Threads' section of the HeapHero report itself we are reporting the thread dump analysis problems. For more details on how to use this feature refer to 'section 6: Thread dump analysis in HeapHero' in https://blog.tier1app.com/2016/10/30/enterprise-edition-admin-manual/ + Fix the object creation rate metrics in Z GC algorithm. + Advanced search panel wasn't loading properly thread dump analysis in Safari browser. Now it has been fixed. + Some customers configure S3 to store the heap dumps. When uploading the heap dumps from the HeapHero server to S3, heap dump file handles weren't closed properly. Due to which heap dump file wasn't deleted even after processing. Now this issue has been fixed. + Fixed several UI/UX stabilization bugs.