Mezmo 2026: Benefits, Features & Pricing

I love the simplicity of LogDNA. It works well for our small environment and seems to have the ability to scale up. The pricing structure makes sense and suits our needs. It's also super easy to install and set up on our servers. I've managed to add it to the provisioning system that we use.

Nothing, at the moment it suits our needs perfectly.

After struggling for years with tail-ing the logfiles of our servers, some genius told me that I should have a look at LogDNA. With their low pricing, I could hardly imagine that they offered quality software. But they do! Once setup at the server, it's easy to create filters (based on server, process, tag or level) to create custom views. So, for example, you can set a view to show all log entries from an error level for a certain process. On top of that, you can also create alarms for views to receive notifications at a certain treshold.

For 99% it does what I expect it to do. The only downside over the past years was that occasionally it was a bit slowish with realtime live updates. But most of the time it's pretty fast.

The interface is quite nice. It is also priced well for high volume. Lastly, it integrates well with other platforms, in particular the Heroku setup is really nice.

* The indexing lag lately has been a bit high. Sometimes we get alerted to errors in Slack from our apps and it takes a few minutes before we can read the logs to see what happened. * The search is a little finicky. It'd be great if we could toggle between full text searching and searching using special characters so we didn't have to escape special characters all the time. * It's awesome that LogDNA serves as a single store for all app logs. However the UI for selecting which apps to display and switching between them feels clunky.

We've used a few other logging tools before, and still struggled with debugging our webapp on multiple servers. Then we found LogDNA, and decided to give it a try. Wow! It's so simple to install, we were up and running within a few minutes. The user interface is clean and intuitive. It's really easy to search keywords (even excluding terms), and jump to timeframes in your own local timezone. You can even type in 10 hours ago and it just works by jumping to the log line with a highlighted marker. It's saved us so much time when diagnosing a problem, tuning our app/server performance, and even when reviewing the logs to predict trends. I also love the alerts and integration with email, Slack, PagerDuty, and even your own Webhook. With a couple of clicks, you can set up the notification rules to trigger an alert. With LogDNA, we always know what's going on at every level throughout the stack.

You can't customize the colors for log levels. Although they have a few preset themes to choose from, you can't fully customize it. For example, it's easy to see the Error level highlighted in red, but for the remaining log levels such as Info, Notice, Warning, Fatal, etc., the colors are the same so you can't quickly skim the logs without reading it.

1. json log ingestion. We were logging our application logs in json formats and when we were looking for the application it fit into it. 2. S3 back up. Sometime we need to search for the older logs and it helps to get it from there. 3. Search. The advanced search really help us to get what we exactly want it. And we go the context quickly(using switch to context) and it really a cool and handy feature to use. 4. Dashboard. Some time out applications misbehaves and flood the logs. It is super easy to find the service using the dashboard by seeing the log ingestion rate. And we use 50s of services.

In the recent release, there is some problem with the search it seems. Getting irrelevant logs

User interface is top notch. So much better than most competitors I've evaluated (which is quite a few actually). Saved views, quick searches and view context functions makes this a joy to use.

Two things are blocking our expanded usage of LogDNA for our much bigger product & team: 1. Reliability. The repeated issues with the remote syslog log ingestion is just not acceptable. I've contacted support about it before, but I won't bother again until it seriously improves. We have to restart at least one logspout container each 1-2 weeks. And there ARE NO ALERTS that things aren't ingesting properly. Basically I don't trust that all log data is there anymore. 2. Pricing. The pricing is great for small log volumes and short durations (as for the product we've migrated to LogDNA). But for slightly larger volumes (say 50 GB) or longer storage (14-30 days), the pricing is too high compared to competitive offerings (from e.g. Logentries). Fewer plans (3 + free) with clear separation by features would be clearer. Costs should increase linearly with storage volume AND retention length (multiplied). This would make pricing clear and logical, instead of using "minimum charges" which is just annoying and stops us from increasing our usage until we reach that threshold. I completely understand the need to raise prices for more value delivered, but it should be structured so that customers clearly perceive the added value. For instance, you should probably add advanced alerts to an "Enterprise" plan, and possibly limit graph usage for "Starter" plans, etc.

- LogDNA is very easy to integrate - takes 5min to setup - LogDNA saves disk space - you dont need to store logs in your server anymore - LogDNA views makes it easy to organize logs based on environment, service, filter, etc - LogDNA alerts enable us to pro-actively identify bugs/crashes before our customers even had a chance to log support ticket - LogDNA makes it easier to expose logs to everyone in the team without having to give them access to the production servers

There is nothing i like least about this product. Maybe the fact that it gets more expensive as your system and users grows, but thats fair and expected

- Very fast search over terabytes of data - Easy to integrate with Slack and other tools - Easy to get up and running overall, especially on Kubernetes. Only two lines of code to implement and start seeing it on the LogDNA dashboard - Lets you control what is being stored, and filtering on ingest means you don’t get charged for filtered data, even if you’re still sending it in for tailing. Pretty fair way of doing pricing. - The overall developer experience is good, and quite intuitive to build graphs and dashboards.

- Takes a while to dig in and figure out all of the features - Alerting is nice, but could use more customization

Really easy to send logs from our servers to LogDNA. We run our workloads on AWS and use the CloudWatch to LogDNA lambda to ship logs to LogDNA... Works like a charm. Love that I can aggregate all my logs from multiple AWS services (a large fleet of EC2 instances and thousands of Lambdas) in to a single log stream. Also really love how I can set alarms for specific strings in the Logs... I get notifications when certain strings appear in the logs which allows me to react to specific events much faster than normal.

Searching logs can be cumbersome. It's not simple booleans, which can make things a bit challenging with complex queries.

- i like the S3 archiving - the search is fast

- sometimes, the search part is not powerful enough. - it will be great if can have a local parser for reading archived data.\