New Pay as you Grow Plans and FREE Live Streaming Tail!

Having launched LogDNA only 6 months ago, we’re thrilled that so many companies now use LogDNA as their go-to live tail and cloud logging solution. Today, thanks to all our customer feedback and recent product improvements, our plans are now more affordable and you only pay for the data you use.

Live streaming tail is FREE

We’re happy to hear how much you love our Live View interface. Now we’re opening it up so that everyone can tail -f like a boss with LogDNA. You can hook up unlimited hosts and sources and save your views for the live streaming within minutes. All for free.

Pay as you grow, starting at $1.25/GB per month

Say goodbye to being constrained by usage buckets and say hello to a simple flat rate. With usage-based billing, we remove the painful guess work of estimating your log volume when choosing a plan. By doing so, we’ve lowered the price of our monthly plans so you only pay for what you use. Now you can start storing your logs with LogDNA for $1.25, that’s less than the price of a cup of coffee!

Choose your log retention

Want to keep your logs around a little longer? No problem, choose between 7, 14, and 30 days search retention at $1.25/GB, $1.50/GB, or $2.00/GB per month. All paid plans include all features, including JSON parsing and S3 archiving.


You can sign up for one of our new plans on our website. If you are already a paid customer, don’t worry, you’re grandfathered into your current plan. You can switch to a new plan anytime by going to the billing page under settings.

Take a look at our pricing FAQ for more information on these simpler pay-as-you-grow options. And feel free to reach out if you’ve got more questions.

We’ve got your back whether you’re just starting out or growing fast. Happy logging!

Product Updates

LogDNA Product Update

Hey everyone,

First, THANK YOU for your support with LogDNA. Many of you have reached out with amazing feedback and questions, we definitely have been listening and working hard to make things happen. It’s been awhile since our last update and we’ve been busy!

Here’s a few major updates we wanted to share with you:

  1. Syslog ingestion now available!

    We now support ingesting logs from rsyslog, syslog-ng, and plain ‘ol syslog. Secure TLS, custom ports, etc.

    You can find more details in our revised host install instructions.

  2. Ingestion Rest API published

    We released a REST-based ingestion API, so you can now programmatically send us your logs!

    You can find more detailed documentation on our API docs page.

  3. Node.JS library released

    Check out this great writeup from Riyadh, who discovered our Node library and integrated it with Winston for logging.

    You can also go directly to our open source Node.JS library on GitHub. We love the open source community, so please feel free to submit feedback as well as submit a PR to contribute to the project.

    We’re missing libraries for other languages, so if you end up writing one, let us know and we’ll feature you!

  4. Elastic Beanstalk

    Check out our integration with Elastic Beanstalk

  5. Funding

    We recently closed a $1.3M seed round from amazing investors. More information can be found here.

This is just the beginning, we have huge plans for the future.

Keep sending us your use cases and requirements and we’ll keep improving LogDNA!

Thank you for your support and happy logging!

Chris Nguyen
Co-founder, LogDNA


LogDNA in the news


We recently raised $1.3 million to keep building out our intelligent logging system and we even received some press about it! Here’s a summary in case you missed it:

Venture Beat:
LogDNA raises $1.3 million to help engineers better manage their servers

Entrepreneurs Chris Nguyen and Lee Liu recently had a “Slack moment” when they realized a tool they had built for their ecommerce company was more valuable than their original product. That formed the basis of their new startup, called LogDNA, which specializes in server management for engineers and people working in DevOps. Today, the company announced it has raised $1.3 million in funding from Initialized Capital and Skype cofounder Jaan Tallinn. Read more…

LogDNA raises $1.6 Million CAD to become “the apple” of logging systems

After Ryerson University grads Chris Nguyen and Lee Liu snagged the chance to go to join Y Combinator as part of its Winter 2015 cohort, the two packed up from Toronto and moved to Silicon Valley to work on Answerbook, an ecommerce solution meant to better target shoppers with highly-personalized emails. Read more…

LogDNA Aims to Make Logging More Predictive with Machine Learning

LogDNA, one of the newest entrants into the already crowded market forinfrastructure log management systems, aims to help companies take a proactive approach to server logging by applying machine learning to detect IT problems. Read more…

Product Updates

The LogDNA agent is open source

The LogDNA agent is a program that automatically reads files and uploads log lines to your LogDNA account. The LogDNA agent is required to view your logs in the LogDNA web app and runs quietly in the background.

Can I trust the agent?

Yes! But if you want to check out how the LogDNA agent works under the hood, take a look at the agent’s Github repository. Essentially, the LogDNA agent authenticates using your LogDNA agent key and opens a secure web socket to LogDNA’s ingestion servers. It then watches for changes to log files specified in the agent configuration. Those changes are uploaded to to LogDNA via the secure web socket in the form of log statements.

Building from source?

The compiled binary for the LogDNA agent is available for Linux, Windows, Mac and Heroku. We’ll continue to expand this to other platforms, but in the meantime, you can download the source code and compile it for your platform. Contact us if you have questions.

Found something?

If you think you’ve found a bug or missing feature with the LogDNA agent, please let us know! Search our issue tracker to see if someone has already reported it. If they haven’t, click here to open a new GitHub issue, and fill out the template with as much detail as possible.

Like to code?

While we pride ourselves in quickly responding to issues, if you just can’t wait, we encourage you to try making the change yourself. Just fork the LogDNA agent GitHub repo  and start coding away! When you’re finished, open a pull request (PR) and we’ll review your proposed changes. Check out our contributing guide for more info.



Customer Stories and FAQs

We love our customers and work to ensure that LogDNA support is quick, easy, and painless. As part of this mission, we would like to share with you a couple of exciting updates:

  • Our website now showcases the great feedback we’re receiving from our customers. Tell us how you feel anytime and be sure to let us know if you’d like to be featured on our home page!
  • Our documentation and Frequently Asked Questions are now consolidated at, and you can chat with us on the bottom right of the FAQ page or email us anytime.

Logs Truly,
– LogDNA team


Log Everything First

When launching an application into production, everyone knows that even the best code can fail for any number of reasons. Implementing strategies that enable you to quickly understand why something is failing and proactively identify the culprit will give you peace of mind and even let you catch some shut eye at night.

The first question developers are always faced with is, how much should I log? 

Troubleshooting no longer just means looking at web server and infrastructure logs, but also custom application event logs, database logs, mail server logs, operating system logs, network logs, and so on. It’s tough to figure out where to look and how to correlate events with each other. Many late evenings are spent by weary dev ops teams grepping files on each server and watching dozens of shells running tail -f.

However, preventing these types of scenarios is where cloud log management solutions really shine. LogDNA’s agent allows you specify the logs you want to watch and you can not only watch them in real time, but also go back in time to see everything that happened. You can also set up views and alerts based on custom smart filters so that you can quickly identify and even prevent situations that have happened before.

Unfortunately most cloud logging solutions force you into deciding what to log right away by charging you on volume. LogDNA takes that question away by starting you off with 50GB/month – for free. There’s so much that goes into building and launching your application, don’t stress about optimizing how much to log on day 1.

This way you have time to figure out what logging events are significant and what views and alerts you need. As you troubleshoot your beta application issues, you’ll undoubtedly dig deeper and add more logging in certain areas and remove logging from others. Keep iterating, keep improving and keep delighting your customers.


Pro tip #2: Log with a view

Ever gotten stuck trying to remember that one grep command used to find the exact log lines you’re looking for? We’ve definitely been there and we know it can happen to the even the most talented dev ops teams.

But instead of having to remember the correct set of grep commands or filters, imagine simply clicking on an aptly named view to bring up all of the pertinent log lines. Welcome to the future of logging – complete with centralized aggregation and cloud access.

Inside the LogDNA web app, you can create these useful and nuanced views in three simple steps:

  1. Set the hosts, apps, and/or log level filters view using the All Hosts, All Apps, and All Levels menus in the top left.


  2. Optionally type search terms you want to select for and even set a start and/or end time window.


  3. Once you’re satisfied with what you see, click the Create View & Setup Alerts button, Name the view, and hit save.


On the left side of the web interface, you can find your saved views, including the one you just created. If you log out, and log back in, you can simply click on your new view and see exactly the log data you’re looking for.


Views are the bread and butter of dynamic logging, so make as many as you see fit. Go on, just view it!