Pinpoint and solve application performance issues down to the line of code. New Relic APM is the only tool you’ll need to see everything in your Java application—from the end user experience to server monitoring. Just add the New Relic jar to your app server to get started. Java monitoring has never been easier.
Get the Big Picture with Java Monitoring
Use the Application Overview Dashboard for general information about your app and to drill down to geographical information, web transactions, JVM statistics, and errors. In one place, you can easily see:
- Response time
- Apdex score
- Throughput (requests per minute)
- Web transactions
- Error rate
- Recent events
- Server Information
Find Java Errors and Problems Fast
See page load times for real users by browser and geography. Find the bottlenecks in your app pinpointed down to the line of code or SQL query. With Java monitoring you can easily see the top five web transactions, their average response times and throughput, with links to transaction traces.
- Trace distributed and SOA applications with Cross Application Tracing and our App Map dashboard.
- Analyze application performance before and after new code deployments.
- Monitor background transactions and web transactions.
- Get alerted to application errors and exceptions - fix problems before they affect users.
Drill Down for Detailed Information
The New Relic UI monitors every detail of your app, from the end user experience, through your servers, and down to the line of code. Give your entire team access to the New Relic dashboard so they can drill down into detailed information about web transactions, including key transactions, browser traces and transaction traces. Browser traces are linked with associated web app transaction traces so you get a detailed end-to-end view of a specific user interaction.
It’s important to understand the types of errors that your users are getting. New Relic reports an error rate as well as error details for web transactions that return a 400 or 500-level error. Error details include the URL that generated the error, status code, count, and the message that was returned to the user. You can configure New Relic to alert you when your error rate reaches a critical threshold. The following HTTP status codes are tracked as errors by default:
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 502 Bad Gateway
- 503 Service Unavailable
New Relic instruments JDBC calls to leading databases. The supported JDBC drivers include: MySQL, Postgres, Oracle, jTDS (SQL Server and Sybase), sqljdbc4 (SQL Server) and Apache Derby.
The New Relic application includes database call time in aggregated data, web transaction breakdown, background tasks, and transaction traces.
For the slowest of the transactions, the New Relic application provides detailed SQL call information. Each slow prepared statement shows both duration and call count. If you choose, you can show the SQL parameters as well. If you are using MySQL or Postgres, New Relic's Slow SQL information includes an explain plan for the query.
Together, these features give you a complete picture of your database activity and where you have the greatest opportunities for optimization.
External HTTP Calls
For many applications, the biggest contributor to the web transaction response time is an outbound HTTP call. These calls may go to services within your system, or to external services such as Amazon S3. The New Relic agent tracks those calls so that you can monitor them in your summary metrics, app map, and transaction traces. You can even configure the New Relic agent to report all or some of the call's request parameters.
The New Relic application can also trace external HTTP calls across your applications. If you have multiple connected applications that use New Relic, you can see the connections between the web transactions in the summary metrics, app map, and transaction traces.
New Relic APM provides visibility into the behavior of your JVM and app server. This information can be crucial for troubleshooting, optimization and capacity planning. Depending on your app server, you will get the following information:
- Memory allocated to different heap and non-heap areas
- Garbage Collector activity
- Loaded and unloaded class count for the JVM
- Active thread count for the JVM
- Active and idle thread count for each thread pool
- The ratio of active to maximum thread count for each thread pool
- Active, expired and rejected HTTP session counts per application
- Active, finished and created transaction counts per application server
Why New Relic?
New Relic APM is the only SaaS application monitoring tool that monitors the entire Java app. With a single product and a single UI, New Relic lets you see the whole stack, front and back, in a real-time performance dashboard you can access anytime, anywhere.
Support for Every Major Framework and Platform
We support all the big frameworks and app servers including:
Read our case studies to see how thousands of companies have used New Relic for Java app monitoring.View Case Studies
“How do I install the New Relic agent?”
Glad you asked! Here's an example process typical for a Java agent installation. Your process may differ depending on the environment you're adding the New Relic agent to.
- Create A New Relic Account
Download the New Relic Java agent
Install it in your environment:
Linux or Mac
Unzip the file into your app's home directory:
unzip newrelic_agent.zip -d /path/to/appserver/Run the install command from the newrelic directory:
java -jar newrelic.jar installOpen newrelic_agent.zip Copy the newrelic folder to your application server's home folder. Open a command prompt and navigate to the application server home. Run the install command from the newrelic directory:
java -jar newrelic.jar install
Restart your application
- A few minutes later, your application will begin sending data to New Relic.
- Once we receive the data, your application will be listed on your dashboard.