New Relic + Loggly: Working Together

 

[obsolete]

We’re really pleased to announce that New Relic and Loggly are partnering to join forces and bring an integrated, multi-faceted view on application and system behavior to stream line root cause analysis. We’ve long been fans of New Relic for monitoring the performance of our systems; it’s pointed us towards a number of areas where we’ve been able to make huge performance gains. When our operations team started to complain that they could see when there was a problem in New Relic, but that it was tedious to correlate the same time range within Loggly, we knew many of our 2,500+ users probably had the same challenge and would love a better solution. So why not build a free one?

Introducing the ‘New Relic – Loggly Integration’ Chrome Extension

Deployed with a few clicks from the Chrome Store, our operations team is now able to pinpoint system performance issues in one click, and identify the source the problem in seconds… aka solve issues faster and get work done. Using New Relic, they get plenty of server stats that tell them when a problem occurred and now they can click through to Loggly and see the log events that directly correlate to the graph that they just looked at within New Relic. What a timesaver, and it is free!

How can you get this goodness?

If you already use New Relic + Loggly, you’re just a minute away from taking advantage of the integration. Download the free extension directly from the Chrome store. If you want to experience the power of New Relic for yourself, we have a special offer with our partnership to offer Loggly users New Relic Standard for Free. Visit newrelic.com/loggly and sign up for free!

Note, because Loggly has an open API, it’ll be very easy to continue improvements to the New Relic + Loggly extension. Let us know if you’d like to see more enhancements or integrations with other products via email or in the comment section.

Happy logging and now with even easier root cause analysis.


2 comments

  • Michel

    3 months ago

    We would like to collect unhandled javascript errors in our website and get them into our in house Logstash cluster. Is there a way you can help with that?

    • Linda Somme

      3 months ago

      Michel,
      We would actually use logstash as a source and then help you monitor and analyze those logs better. Check out the Ultimate Guide to Logging for some more general logging tips: https://www.loggly.com/ultimate-guide/

Share Your Thoughts

Top