New Relic Extension

Introduction

Loggly’s New Relic Extension for Chrome allows you to find any performance issue or error in New Relic, and then find the matching logs in Loggly. We will give you more detail to troubleshoot problems, including what happened before and after the event, what caused the problem, how to fix it, and who was affected.

Complementary Views

Loggly and New Relic can both show the same event or problem, but Loggly can dive deeper into the details. Here is an example of a spike in exceptions in a New Relic application, and a matching graph in Loggly’s time series chart view.

Image 1-1 Image 2

Loggly Gives You Deeper Visibility:

  • Look at warnings or more verbose log levels
  • Check log messages inserted by developers around common problems
  • Trace code path execution to verify your logic and input parameters
  • Trace requests or transactions across multiple applications and servers
  • Validate parameters and data to third party services and APIs
  • Load entire sessions for particular customers or transactions for debugging and customer service
  • Correlate problems with internal systems like apps and databases, and external systems like load balancers and CDNs

Use Cases

Error troubleshooting and root cause analysis
Suppose that New Relic tells you of some errors that your application is experiencing. So you get the proper dashboard in New Relic and focus on the view on the general area of the problem. What next? Now you can get a detailed log-powered view of the exact same error. You see what happened before the error and the actions that lead up to it, you can follow the logical paths that the program took to get there, and you can analyze the behavior and end-to-end application model. You can now quickly understand if it’s an application error, an error propagating from one of the dependencies of the application, or an error that is due to the infrastructure powering the application.

For example, if you find an exception in New Relic called “TablesawException” you can find that same exception in Loggly, and then search for what happened before the exception.
Image 3

Trace performance bottlenecks across multiple applications
Imagine that New Relic tells you about performance issues with one of your apps whose response time is way beyond SLA. How do you identify the bottleneck? Visibility in the application alone is often not enough. Event logs are great for the identification of such issues, especially when you aggregate logs across all your applications and systems. From this view, you can trace the requests or the transactions across multiple applications, or from client side to server side, in backend or middleware layers, or dependent services that failed to respond in time.

Using The Extension

Getting Started

To get started, first enter your Loggly subdomain. Optionally, there are two checkboxes which let you enable matching for syslog hosts and the New Relic application ID, which are described below. Now you’re ready to use the search link on the top of the application pages or highlight any text to search in Loggly.

Application Search

We’ve added a search link to the top of every New Relic application page which lets you find the matching logs in Loggly. It will include the same time range you’ve selected in New Relic. Also, if you’ve enabled the option for syslog hosts it will include the hostnames from the server dropdown box by searching syslog.host in Loggly.
Screen Shot 2014-04-01 at 1.36.36 PM

Highlight To Search

You can also highlight any text such as an error message, and search for that error message in Loggly. We make the search results contextually match the same time range, servers, and New Relic application. This lets you get the same view in both New Relic and Loggly.
Screen Shot 2014-04-01 at 1.37.10 PM

Configuration Options

  • Loggly Subdomain

Enter your loggly subdomain. You can find this by logging in, then looking at your browser address bar. It will be in the format of “x.loggly.com” where “x” is the subdomain.

  • Syslog Hosts

This option will search only the servers in the New Relic application you are viewing, provided you include the syslog hostname in your logs. It gets the server names from the New Relic application drop-down box and matches them using the syslog hostname in Loggly. It will search syslog.host and does not currently work if you send your logs over HTTP.

  • New Relic Application ID Tag

This option will search only logs with your current New Relic application ID, provided you tag your Loggly logs with the same ID. You can get your NR application ID by going to an application page, then in the URL it will be the second string of numbers at the end. For example, in this URL https://rpm.newrelic.com/accounts/56636/applications/2931030/traced_errors the application ID is 2931030. You would send you logs with tag:2931030.

  • Filter Special Characters out in Search

This option will remove special characters before sending the search term to Loggly. This will remove characters that can cause syntax errors in the search.

Where To Get It

Download it from the Chrome Web Store today!

Thanks for the feedback! We'll use it to improve our support documentation.


Top