CrashFeed is a fanatastic solution for enterprises to monitor crashes and pinpoint problems, end to end. CrashFeed provides visibility into application behaviour as well as keeping you informed of misbehaving code before your users can write negative reviews. The solution is delivered as a service and enables companies to track their entire infrastructure starting from client application all the way back to the server-side applications.. For maximum flexibility, enterprises can quickly instrument mobile clients, servers, or the entire application stack using a single line of code in each.
The benefits of using CrashFeed are:
- Achieve a holistic view of your application – The unified dashboard aggregates and displays all events from client to server-side.
- Identify issues in real-time – developers get instant notifications when the application events are triggered. In addition to being available on the unified dashboard, events can be forwarded to assigned individuals in the organization via email or SMS.
- Reduce time to find bugs / errors – Bugs can be elusive and replicating the error to get information about the crash can be extremely time consuming and difficult. CrashFeed solves this problem by giving developers extensive information of the system right before the crash.
We’ll show you how easy it is to set up CrashFeed as a Java Agent in Jelastic. So, let’s get started!
1. Create an environment
1. Go to jelastic.com and sign up if you haven’t done so yet, or log in with your Jelastic credentials by clicking the Sign In link on the page.
2. While in the Jelastic dashboard, click the Create environment button at the top left.
3. Pick your application server (for example, Tomcat 7) and specify your environment name, for example, safeserver.
Wait just a minute for your environment to be created.
2. Upload CrashFeed
1. Navigate to crashfeed.com and create a free account.
2. Download the CrashFeed agent.
3. Extract files from the zip package you have just downloaded.
4. Go back to Jelastic’s dashboard and upload crashfeed.jar and crashfeed.json to the home folder. Update crashfeed.json with your CrashFeed API key.
5. Open variables.conf file (server folder) and specify the path to jar file according to environment variables:
Tomcat
-javaagent:/opt/tomcat/temp/crashfeed.jar
Jetty
-javaagent:/opt/jetty/home/crashfeed.jar
GlassFish
-javaagent:/opt/glassfish3/temp/crashfeed.jar
More information about environment variables.
Don’t forget to save the changes and restart Tomcat!
Important: Installing CrashFeed for Jetty isn’t any different from what we did for Tomcat – there’s the variables.conf file that is used for specifying the auxiliary JVM arguments. Installing CrashFeed for Glassfish is slightly different as instead of variables.conf Glassfish uses the domain.xml configuration file. So we can either modify the configuration file, or set the arguments via Glassfish administration console. See this for details: Setting Environment Variables in Glassfish
3. Application deployment
1. Upload your WAR file to the Deployment manager.
2. Deploy it to the environment you have created earlier.
4. Start CrashFeed
Now you can go to the CrashFeed web site, log in, and monitor your application.
