LogDNA Overview

LogDNA is the #15 ranked solution of our Log Management Software. It is rated 4.5 out of 5 stars, and is most often compared to ELK Logstash: LogDNA vs ELK Logstash

What is LogDNA?

LogDNA is a powerful, multi-cloud log management system that aggregates all system, server, and application logs into one modernized platform. Centralize, monitor, store, tail, and analyze logs in real-time with one simple command-line or web interface. Setup takes just 1-2 minutes. Deploy as a cloud SaaS solution, on-premises using your own infrastructure, or as a hybrid solution. Empower your engineers with the exact logging solutions they need so they can focus on what they do best - create quality products.

LogDNA Buyer's Guide

Download the LogDNA Buyer's Guide including reviews and more. Updated: November 2020

LogDNA Customers

Instacart, Asics, Lime, Salesforce

LogDNA Video

LogDNA Reviews

Filter by:
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Theodore Omtzigt
President and Founder at STILLWATER SUPERCOMPUTING INC
Real User
Top 5
Mar 24, 2020
Has vastly increased our ability to reach SLA targets consistently

What is our primary use case?

In terms of primary use case, LogDNA is our root cause analysis for on-call channels and we're now also using it for load testing. We have a silverized service in production. When an issue hits the on-call channel, meaning a customer receives some type of service issue, we receive an alert and use LogDNA to RCA why that particular alert fired. We use it to trace customer requests and customer interaction, as well as studying our own service to make sure that we don't trip up in the transactions or on the services we depend on. The product is our only SIEM. We've become more skilled at using it… more »

Pros and Cons

  • "The solution aggregates all event streams, so that if there are any issues, it's all in the same interface."
  • "No ability to encapsulate a query or a filter, and communicate or share that among the team."

What other advice do I have?

There are enough moving pieces that can go wrong, that require a very broad skill set in a team. I would advise others to make sure that you have the breadth of skills in your team to integrate properly in your whole service, to be able to customize it and finally, to actually use it properly. These are nontrivial things because you need to understand the interface with your own software, to use the tool properly and then to have some skills so that if something goes wrong, you can figure it out and fix it. If you look at the progression, a year ago we were missing the SLA target. Now, we can…
Theodore Omtzigt
President and Founder at STILLWATER SUPERCOMPUTING INC
Real User
Top 5
Sep 19, 2020
It consolidates all logs into one place and provides required features and functionalities

What is our primary use case?

It is our sole cross-correlation logging backend for some IBM services. We have a combination of LogDNA and Sysdig for root cause analysis and customer events. LogDNA is related to the operations of the service. Sysdig is somewhat nice in the sense that it also gives us some backdrop when there are any issues with respect to resources and other types of metrics-based constraints.

Pros and Cons

  • "LogDNA consolidates all logs into one place, which is super valuable."
  • "Every once in a while, our IBM cloud operational implementation gets behind. Sometimes, when we have a customer event, we do not get access to the latest logs for about 30 minutes, particularly for the sites that are heavily utilized. This is clearly not good. It is impossible to RCA when you can't look at the logs that pertain to the time period in which the event occurred. It could be more of an operational problem than a feature problem. I don't have visibility about whether it is a LogDNA issue or just an operational issue."

What other advice do I have?

We haven't had anything yet that we couldn't do through LogDNA. Feature-wise, it is solid for us. From a functionality point of view, that is, finding stuff and doing RCA and other things, we're able to find what we're looking for. We don't have any constraints at this point. I would rate LogDNA an eight out of ten.