RELEASE YCRASH 0_32 NOTES
--------------------------

1. UI/UX enhancements

 We have made significant enhancements to our UI/UX layer. UX has been made more intuitive and natural. We have made UI adaptive and responsive for various form factors (Mobile, Tablets, multiple versions of browsers).

2. key-registry.xml from remote storage

 YCrash APIs are invoked with one global API key. If you are planning to roll-out our service enterprise-wide, you might want to give unique API key for each organization in the enterprise. This approach will provide you with more granular control. If you decide to grant access or revoke an organization from accessing the service, this granular control will be of help.
 
 So far, this file has to be present in the local disk. From this release, this file can be placed in the remote storage. You can create a file with 'key-registry.xml'  and place it in the remote storage's root directory.
 
3. license.lic from remote storage
 
 license.lic is the file where licensing limit, expiration date,... is stored. So far this file has to be present in the local disk. From this release, this file can be placed in the remote storage. You can drop this file in the remote storage's root directory.
 
4. SSL Enablement

 You can start to do SSL termination in the YC Server itself. To do SSL termination on the YC Server, just add the following parameters to the launch-yc-server.sh:
 
 --enable-client-auth true -Djavax.net.ssl.keyStore=/opt/my-keystore -Djavax.net.ssl.keyStorePassword=my-keystore-password
 
 Replace "/opt/my-keystore" with your server's keystore file path.
 Replace "my-keystore-password" with your keystore's password

5. Upload only GC log, Heap Dump, Thread dumps only: 

In the previous releases, the YC agent script expects a process ID as input. YC Agent will capture GC logs, heap dumps, core dumps + other artifacts (top, top -H, netstat, iostat,...) from this live process. Starting from this release, you can invoke the YC agent without passing process Id. You can invoke the agent by only specifying the GC log file path, thread dump file path, heap dump file path with following arguments:  

-gcPath
-hdPath
-tdPath

YC agent will transmit only these artifacts to the YC Server and analysis will be completed.

6. Heap Dumps in remote storage

Even though remote storage was configured in the earlier release, heap dumps were stored in the local disk only. In this release, if remote storage is configured, heap dumps will be stored in the remote storage.

7. Download Heap dump directly from Remote storage

In the YC report there is a button 'Download heap dump'. When user clicks on it, heap dump will be downloaded from the YC server to the user's local machine. Now if you are using remote storage like (AWS S3, Pure Storage,...), this heap dump will be directly downloaded from the remote storage. But you will have to make proper read permissions are given on the remote storage configuration to facilitate this download.

8.Bug fixes

We have made several bug fixes to improve the stability and functionality of the application.