Getting Started with Loggly Part 2: The Cool Stuff!

This is a continuation of part 1: Getting Started with Loggly.

Note: Apparently waiting hours for account generation isn’t a thing according to the fine folks on twitter @loggly.

@_JohnathanLyman Creation takes a few sec so likely something happened during form validation. Perhaps try again or DM us the subdomain you typed in

— Loggly, Inc. (@loggly) March 15, 2015

Now that we’re signed up, let’s get down to the good stuff!

The first thing I want to do is start tracking Linux. The core of my site is Ubuntu (among other things). Loggly makes this easy. All I need to do is click the Linux icon on my account’s main page.

It really is as simple as copying the two lines of code and running them with superuser access. Within a few seconds, Loggly grabbed a hold and started showing me cool stuff!

It’s pretty empty now, because I literally just started tracking and I’m only tracking Linux. With time this will become more populated and more interesting to parse through.

Moving on to other applications, now. I want to start tracking nginx. Nginx is just one of the apps Loggly can track. The list is massive.

Getting Nginx set up was just as easy as Linux, although Loggly believed my Nginx logs weren’t of a proper format. No matter, they’re coming in great.

Getting MySQL set up isn’t a one-click process like the others. This requires MySQL to do some extra work and get a bit re-configured. No worries, it’s nothing extravagant.

Setting up PHP was a breeze, and I like a good breeze.

Once everything was added like I wanted, I started poking through my logs to see if I could really find good data without hassle. Turns out, I can.

What’s better than watching someone from China try to hack into your system via SSH by trying to log in as the root user?

Nothing 🙂

I’d recommend Loggly to anyone who wants to consolidate and be able to parse and search through their log data. You might not need the heavy plans, I know I don’t. It’s still good to be able to look at events as they happen in real time with an interface that doesn’t suck and from anywhere in the world without having to log into your system.

Go check out Loggly, right now. You’ll enjoy it, for sure!


Getting Started with Loggly

I love logs. I love massive amounts of data. I have this thing where if I feel I can consume and process tons of data by doing something menial and useless, I’ll do it.

One thing I don’t really do though is keep tabs on the logs for my site and its services. This is where Loggly comes in, and this is my experience getting it set up.

Signing up was pretty easy. I just went to loggly.com, clicked Sign Up in the top right corner, filled out a few things, and waited patiently while their systems used magic fairy dust and unicorn blood to construct my logging instance. They provide a full 30-day trial that gives a user full access to all features to determine if it’s really right for them. After 30 days, it drops down to their limited free tier, which is still good for small people like me.

I’m writing this as I go through their service, so let’s take a moment to talk about what Loggly actually does.

The whole goal of Loggly is to provide centralized log management without the need for agents. This allows sysadmins or anybody who cares to view and track log data in real time. You can search through logs as they come in and graph out instances of particular events to track down issues as they’re happening.

Logy allows you to track logs from almost any source. Their list is pretty exhaustive if you ask me:

  • Windows
  • Linux
  • Apache
  • Nginx
  • IIS
  • JavaScript
  • Tomcat
  • MySQL
  • Microsoft SQL Server
  • Rails
  • Python
  • Django
  • MongoDB
  • PHP
  • Java
  • Ruby
  • Node.JS
  • .NET
  • Docket
  • Puppet
  • Chef
  • FluentD
  • AWS Cloudtrail
  • AWS S3
  • and Heroku

That really is a pretty big list.

I mentioned that you can get started for free than that there’s a free tier, but let’s talk about what that actually means and the other options that are available.

The free tier gives you the basics including searching and filters, persistent workspaces, and built-in alerting. The standard tier ($49/month) gives you 1GB/day of log storage and 7-day retention, unlimited users, built-in alerting, customized dashboards, and more.

Moving to the Pro tier is where you start getting some of the more tasty features.  You get peak overage protection, AWS S3 archiving, telephone support, and more. The default plan grants 15 days of retention at $109/month, but if you need more than that, you’re more than welcome to it: 10GB/day for $499, 50GB/day for $2500 and more. If 50GB/day and $2500 sounds like a lot, don’t worry, it is. 50GB of log files in a day though is a lot and if you need that kind of support, you’re not too worried about the price.

The second half of this post is to follow after my account is set up… see you soon!


page 1 of 1