Loggly Top 10 Developer and DevOps Blogs of 2014

Looking back at the content we wrote and shared in 2014 is a great way to get a pulse on our audience, the market and gain a directional head-start on the trends picking up steam that promise to be even bigger in 2015.

What were the topics that our audience (you!), cared about in 2014, by eyeballs, page views and engagement? Specifically what were the Developer and DevOps blog posts that you couldn’t stop reading?

1. What 60,000 Customer Searches Taught us about Logging in JSON

   Understanding how our customer’s search their logs is extremely powerful as it allows us to improve their process and the clarity (and friction uncovered) drives our product enhancements even further. Search efficiency is a key KPI because time to resolution is critical one for our customers. Discover what we learned reviewing 60k searches.
   Read More » | Tweet this article »

2. How to Centralize Logs from Docker Containers

   While only live for a few weeks, our post on centralizing logs from Docker zoomed up the charts to number three, so popular that over 10% of the visitors share the post socially! While companies rely on Docker to shorten release cycles and implement continuous delivery cycles and we covered how Loggly adds power to Docker Logging to extend visibility into the solution.
   Read More » | Tweet this article »

3. Nine Tips on Configuring ElasticSearch for High Performance

   We built ElasticSearch into the fabric of our core Loggly functionality. In the process of scaling to ingest and process way more than 100,000 events per second, we learned some very important lessons about how to set up ElasticSearch for High Performance that the web couldn’t get enough of as the article has remained a top 10 website page view everyday.
   Read More » | Tweet this article »

4. How Loggly Dynamic Field Explorer Changed Everything

   Developers and DevOps told us loud and clear in a survey, that over 70% of their time solving operational issues was spent finding the problem versus fixing it. We launched Dynamic Field Explorer and fundamentally changed how people perform log analysis and operational troubleshoot by providing answers ahead of search. After a few days in beta, we knew our customers loved it as much as we did and it’s only gotten better.
   Read More » | Tweet this article »

5. Five Things Every Developer Should Know About Syslog

   Loggly customers send us data without installing agents on their machines, and using a Syslog utility is one of the most common methods. So when one of our developers offered to dissect Syslog, one of the most widely adopted logging standards to uncover a handful of underappreciated items I cleared the table and handed him the reigns. Here’s five tips for getting more out of Syslog.
   Read More » | Tweet this article »

6. AWS Cloudwatch: Log Management is the New Kid on the Block

   Do you speak AWS? If so, by default you know of Werner Vogels, AWS CTO. Anyone building a business on the backbone of Amazon Web Services would be smart to follow his vision (and @Werner on Twitter) as when the #CloudFather speaks… everyone listens. I couldn’t have been happier to hear Werner keynote AWS NY Summit and talk about the importance of logs and log file management for the business.
   Read More » | Tweet this article »

7. What We Learned About Scaling with Apache Storm

   When our 2013 AWS re:Invent session became the most-watched customer session at ReInvent, we knew the topic (building SaaS at massive scale) wasn’t going away anytime soon. When we retooled our backend and moved away from Apache Storm we knew it would draw a ton of interest and questions, so here’s what we learned about Storm and why we left (it’s not you it’s us).
   Read More » | Tweet this article »

8. Why Loggly Chose AWS over Route53 for Elastic Load Balancing

   One of our most viral pieces, the blog went viral 4 times on Reddit and HackerNews since it was posted and generated so much interest that AWS asked us to speak at 2014 AWS re:Invent to outline our success story. Read for yourself how we put it into action.
   Read More » | Tweet this article »

9. How to Use Loggly to Report on Errors and Exceptions

   One of the joys of SaaS done right is talking to endless customers about how they use the product. When we dove into using Loggly for error reporting (our second ranked most popular) the conversations were passionate so our Product Manager compiled the top ways to rank errors and share them with development teams to share the knowledge.
   Read More » | Tweet this article »

10. Six Critical SaaS Engineering Mistakes to Avoid

    The experience of building seven different cloud-based SaaS products holds important product lessons (and life lessons) that should not be ignored. Manoj Chaudhary, Loggly CTO and VP of Engineering, outlines the six critical mistakes that separated the companies that rose fast from those who stumbled in one of our most shared posts.
    Read More » | Tweet this article »

Honorable mention: Launching the ‘Unofficial Crowdsourced AWS re:Invent Guide’

The growth of AWS is legendary. With it, the interest (and attendance) at AWS re:Invent, the superbowl of the cloud world has grown exponentially. When over 12,000 of the world’s top developers and DevOps gathered in Vegas… we had just the idea to help them make the most of the event and released: “The Unofficial Crowdsourced AWS re:Invent Guide”. We put the best sessions, booth swag and parties into one place and attendees (and vendors) love it so much we turned it into a mobile friendly version to use from your phone.

Read More » | Tweet this article »

The Loggly and SolarWinds trademarks, service marks, and logos are the exclusive property of SolarWinds Worldwide, LLC or its affiliates. All other trademarks are the property of their respective owners.