Dear Customers,
We have been working to constantly improve our EM Cluster Upgrade experience since the last couple releases and we are nearing another milestone, which when available would further simplify the EM Cluster upgrade experience! We appreciate if you could spend a couple minutes of your time to read through this blog post and then take part in this one-off activity. We expect it to take not more than 30 minutes of your time and it would help us immensely to deliver a quality release.
Please allow us to explain more:
What is this about?
- We are working on a solution that would ease the way we upgrade the EM Clusters. And not just ease, it would also drastically cut down the time it takes to do an upgrade. We expect it to reduce the time it takes to do an upgrade from ~4 hours to about 30-60 minutes.
- We have developed a jar, which when run in your environment (test or production – as per your choice), would generate a few text files, which contains information about your environment.
Why have we developed this jar file?
- Before we go GA, we want to test the solution in an environment that resembles as close possible our customer’s environment. Based on the data we get from you, our teams will setup internal test environments on which we are going to run tests to find and mitigate issues as early possible
What data does this jar file collect?
It operates in two modes:
Min mode
OS info:
- Disk/partition usage
- Mount information
- Network Information
- Kernel logs
- Global info (uname)
- CPU info
- Memory info
- Process info
- Size of EM_HOME
- Size of external SS
- Size of external Traces
EM data:
- Logs
- Process based APM discovery
- Collection of: collect IntroscopeEnterpriseManager.properties, IntroscopeWebView.properties, domains.xml, agentclusters.xml, tess-db-cfg.xml, realms.xml, apm-events-thresholds-config.xml
Max mode (default mode)
- All from MIN level
- Collect EM_HOME/config directory
- Collect 2 days of SS
- Collect SS Metadata
- Collect 2 days of traces
- Collect SQL data (CEM data are stripped down to max 1K rows, geolocation tables are stripped completely)
Where can I download this jar file from?
The jar file titled "data-collection-utility-1.1.jar" is attached to this post. Please download it directly from this location.
What does this jar file not do?
- It doesn’t run as a background daemon.
- It doesn’t send any information to us automatically. It creates a zip file that contains text files, which upon verification, you could share it with us.
What steps you could perform after running the jar?
- Check the contents inside the text files and delete any information you are not comfortable sharing with us
- Open a Support Ticket (S4) and upload this zip file to that ticket (in this way, your data is uploaded in a secure manner)
What are the instructions to run this jar file?
- Navigate to EM home on MOM and collector
- Run: java –jar name.jar
Remember there are two modes. The default is max mode. To customize the mode in which you want to execute it:
Add - -run.level=min (default is max)
For example: java –jar name.jar --run.level=MIN
To customize temporary folder that is used for storing the data before they are packed:
Add - -run.temp=/path/to/folder
We can also setup a live webex to help you run this jar file. Please write us an email @ Chaitan.Shet@ca.com or Zaneta.Svozilova@ca.com if you would like to avail this option and we will be happy to setup a call the very next day. If you need any guidance on raising a Support ticket, please write to us @ Ruth.Wunderle@ca.com
Your participation is optional, but should you choose to participate and we would be very happy if you help us with your time and participation, the expectation is to run this jar file, verify its contents, edit/delete incase you are not comfortable with sharing something and ship the zip file back to us, if possible within a week’s time you see this email request from us.
Thanks for reading this far.
Best Regards,
Chaitan & Zaneta
Product Owner – CA APM