Product Updates

April Product Update

Get ready for a LogDNA product update – power user edition! This month we’ve added a number of powerful features to fulfill many of the awesome use cases we’ve heard from the LogDNA community. But first, we have an announcement!

Microsoft’s Founders @ Build event in San Francisco

LogDNA is speaking at the Founders @ Build event hosted by Microsoft. The purpose of the event is to bring cool companies together like Joy, Life360, GlamSt, GitLab, and LogDNA to share their experiences and perspectives. They’ve even invited Jason Calacanis (Launch) and Sam Altman (Y Combinator President) to weigh in. We’re excited to be part of these conversations informing the next generation of startups, and want to invite you all as well. You can check out the full agenda and register here.

And now for our regularly broadcasted product update.

Export Lines

By popular request, you can now export lines from a search query! This includes not only the lines that you see in our log viewer, but thousands of lines beyond that as well. This is particularly useful for those of you who want to postprocess your data for other purposes, such as aggregation. You can access this feature from within the View menu to the left of the All Sources filter.

We also have an export lines API, just make sure you generate a service key to read the log data. More information about the API is available on our docs page.

Web Client Logging

In addition to our usual server-side logging, we now offer client-side logging! This enables some new use cases, like tracking client-side crashes and other strange behavior. Be sure to whitelist your domains on the Account Profile page to prevent CORS issues.

Line Customization

When standard log lines just don’t cut it, this feature allows you to customize the exact format of how your log lines appear in the LogDNA web app. This includes standard log line information, such as timestamp and level, as well as parsed indexed fields. You can check out this feature by heading over to the User Preferences Settings pane.

Heroku Trials

We’ve officially added a trial period for our Heroku add-on users. For new accounts that sign up to our Quaco plan, we now offer a 14-day trial, so Heroku users can get the full LogDNA experience before they sign up for a paid plan.

Other Improvements

  • logfmt parsing – Fields in logfmt lines are now officially parsed.
  • Exists operator – Search for lines with the existence of a parsed field with fieldname:*
  • Disable line wrap – Under the tools menu in the bottom right.

And that’s a wrap, folks! If you have any questions or feedback, let us know. May the logs be with you!

Product Updates

March Product Update

It’s time for another product update! We’ve been working furiously for the past month to crank out new features.

Terminology change

First and foremost, we’ve made a major terminology change. The All Hosts filter has been renamed to All Sources. This allows us to account for a wide variety log sources, and as we transition, other references to ‘host’ will be changed to ‘source’. But don’t worry, the Hosts section of the All Sources filter will remain intact.

Filter Menu Overhaul

Internally dubbed “Mega Menu”, this is a feature we’re very excited to have released. The All Sources and All Apps menus now feature a unified search bar that will display results categorized by type. No more hunting for the correct search bar category within each filter menu.

Dashboard

By popular request, we’ve added a dashboard that shows your daily log data usage in a pretty graph as well as a breakdown of your top log sources and apps. You can access the dashboard at the top of the Views section.

Ingestion controls

If you find a source that is sending way too many logs, you can nip it in the bud by using the new Manage Ingestion page. Create exclusion rules to prevent errant logs from being stored. We also provide the option to preserve lines for live tail and alerting even though those lines are not stored.

Comparison operators

For you power users out there, we’ve added field search comparison operators for indexed numerical values. This means you search for a range of values for your indexed fields. For example:

response:>=400

This will return all log lines with the indexed field ‘response’ that have values greater than or equal to 400. More information on comparison operators is available in our search guide.

Integrations

We’ve added PagerDuty and OpsGenie integrations for alert channels, so you can now receive LogDNA alert notifications on these platforms.

On the ingestion side, we’ve added an integration for Flynn. You can send us your logs from your Flynn applications by following these instructions.

Archiving

To open up archiving to more of our users, we’ve added Azure Blob storage and OpenStack Swift archiving options. You can access your archiving settings here.

Other improvements

  • Share this line – Use the context menu to share a private link to the set of lines you’re looking at or share a single line via a secret gist.
  • Search shortcut – Access the search box faster by hitting the ‘/’ key.
  • Switch Account – Open multiple tabs logged into different organizations using the Open in New Viewer option under Switch accounts.

That sums up our product update. If you have any questions or feedback, let us know. Keep calm and log on!

Product Updates

Product Update February 2017

It’s been awhile since our last update, but we’re busier than ever. We’ve released a huge number of features during this time, with many more on the way. Without further ado, we proudly present the February 2017 LogDNA product update!

Platform Integrations

We added a host of new platform integrations (no pun intended), but we’d like to highlight our easy to install Kubernetes integration. We believe containers are the future, so we want to be your container logger of choice! Our new integrations include:

  • Kubernetes
  • Docker
  • Fluentd
  • CloudWatch
  • Cloud Foundry

Installation instructions for integrations are available on our website.

Code Libraries

As per popular request, we’ve also added several new code libraries:

  • Ruby
  • Rails
  • Python

You can check out our open source code libraries on GitHub. We welcome contributions!

HIPAA compliance

There’s a revolution happening in healthcare tech, and we want to be a part of it. We’re officially offering HIPAA compliant logging! Whether you’re a healthcare provider or vendor, we’ve got you covered, and will happily sign a Business Associate Agreement (BAA). See our HIPAA page for details.

Features

While there are a ton of new features, we especially want to mention line context. With line context, you can expand any individual log line and view field information as well as line context for that host or app. Count on many more features coming to this context menu :). More information about line context is available in our docs.

In addition to line context, we’ve also greatly improved alert management, as well as added HipChat notification support and a Slack app. For those of you with more than 12 views, we’ve even added a handy dandy View Finder to help you search them. Pro tip: you can use the shortcut CTRL + K to bring up the View Finder.

Documentation

Creating all these features means creating lots of docs. We’ve not only added docs for the new features, but a whole new set of extensive guides that contain no shortage of valuable information. Check out our guides below:

The Future

We strive to create innovative and useful new features, but we can’t do it without you. Your suggestions and feedback are actually factored into features we release, so thank you! Speaking of which, we have some pretty cool new features in the works:

  • Line tags powered by machine learning
  • Git blame for your logs
  • Swift log archiving

If you’re interested in being a beta tester, let us know at support@logdna.com and we’ll enable beta features for your account as well as notify you as new ones become available.

Community

We want to give a shoutout to all our awesome customers. Thank you all for your feedback and support, we wouldn’t be here without you. Log long and prosper!

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

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.

 

Product Updates

Deployment Tracking with LogDNA Live Streaming Tail

 

You’ve deployed a new feature into production. You’ve done your unit testing, fixed lots of bugs, your code is awesome. Now it’s time for hundreds/thousands/millions of users to break…err…use your feature.

You’re diligent about track usage in real-time and get customer feedback when something goes wrong. You track the performance and response time impacts on the server.

All is good…except…that feature isn’t quite working for a specific group of users. Now what?

With LogDNA, you can monitor for stack traces and exceptions in real time. In your browser, you can tail -f like a boss and see real-time logs from all your app sources, Nginx, and Redis. Since you can combine data from multiple sources and see related events, you can do a thorough root cause analysis and surface hard-to-find bugs.

To track your new feature in LogDNA‘s dashboard,  you can either watch the error happen in real time, go back in time to when you deployed or jump directly to an error that happened in the last hour.

Screen Shot 2016-05-17 at 10.45.26 AM

Here are some examples of how to use LogDNA’s powerful search:

  • Find lines that contain “403 Forbidden” and “login”.
Search: "403 Forbidden" login
  • Find lines that contain “ClassCastException” or “NullPointerException”.
Search: ClassCastException OR NullPointerException
  • Exclude lines where the field LEVEL is “info” starting from 2 hours ago.
Search: -level:info

Timeframe: 2 hours ago
  • Find lines that contain “‘str’ object” but does not contain “TypeError” starting from last friday 10am.
Search: "'str' object" -TypeError

Timeframe: last friday 10am
Here’s other examples of what you can put in the timeframe: an hour ago, 5:42am, yesterday 1pm, 2/24 2:30pm

Now that you’ve zeroed in on the problem, you can always set your query up as a view and set up alerts to notify you if this ever happens again.

When you use LogDNA’s Live Streaming Tail, you’re getting

  • a real-time stream thats updated as soon as LogDNA receives new log data
  • a single view of data from multiple sources
  • to focus on important data with powerful searching, filtering, highlighting capabilities
Let us know what you’ve been doing to surface those hard to find bug in production today. It only takes minutes to see your live streaming log, get started with LogDNA  now.