Mezmo Reviews

LogDNA is incredibly easy to use and set up. Great features like Real-time alerts and Usage Quotas are available in all paid plans. Pricing is reasonable and pay-as-you-go means it's perfect for hobbyists and small businesses. You can set up Usage Quotas to ensure no surprise bills.

We had a couple of months of unexcepted high bills after a server improperly handled a recurring error but since they added Usage Quotas, it's no longer an issue and I have better trust in the service.

LogDNA allows quick and easy access to log history. Searching is fast. Real-time alerts allow you to react to production issues quickly. Being a cloud service means there's less configuration and maintenance so the team can focus on our product.

LogDNA is easy to use. It can be configured to display appropriate information for developers, IT support staff, and managers. We often release new code multiple times a day and having immediate access to any issues that arise is critical. LogDNA has made use more responsive and productive.

We have no complaints. Learning the full capacity takes time - in fact, years later we are still finding new was to use its features.

Most often we use it to find unintended consequences to database or code changes. I imagine that like most organizations we face the problem of legacy technology getting in the way of desired improvements. LogDNA allows us to release major improvements and then discover the edge cases where that has caused problems.

- Alerts to slack

- Conditions on alerts

- Saving views and filters

- Ability to live-tail

- Searching through logs and quickly getting the results.

- More language integrations would be better to ingest logs in an easier way.

For practically all of the IT companies out there, logging is not a core function, yet it is an absolute necessity. This is where LogDNA comes in. It works wonderfully and completely gets out of our way.

We push logs into it from our .NET servers via a Serilog LogDNA sink. The ability to filter logs with ease and to later create views out of those filters is amazing. We are always utilizing the live tailing feature during new version deployments. We also have many alerts set up for the views, which send alerts to Slack. The way alerts can be configured is very intuitive and combining filters and alerting conditions allows for very precise and meaningful alerts to be sent to us.

At the current pricing level, it would be wrong not to use LogDNA.

Nothing can replace a purpose-built tool meant to ingest and aggregate log data. There are other options out there, some of which are built directly in to the cloud provider my business uses. None stand a chance in being as easy to use as LogDNA.

We love how easy LogDNA makes it to see all our log data in one place. Its a snap to focus on a single server or app, or search for a specific log entry,

The ability to dynamically group hosts could be improved.

We utilize blue/green deployments so our hosts are constantly being rotated out. We also have LogDNA running on our staging hosts. Its challenging to show an always up-to-date view of all our production hosts without manually adding new hosts to the view after a deployment. If we just "select all" hosts, we'll end up with a view that has both production and staging in it.

We're solving the problem of showing an aggregate view of all our log data in a way thats easy to understand, easy to search, easy to export, etc. LogDNA is just so much more user friendly than any other similar service we've used.

In Gemunion we help startaps to set up their business from a technical perspective. We use monopero architecture to setup different microservices and it is really easy for us to filter logs by microservice and instance as well as set up notifications about errors to telegram and slack

I would like to be logged from more than one account at a time. Hate to switch between multiple company's accounts

Not all things should be done by yourself. If the service is good and has a reasonable price you should use it instead of reinventing the wheel

We use logdna as part of our error pipeline. We used papertrail before it was terrible from all sides starting from price. we also tried a local graphana setup but it takes much longer than just connecting to logdna.

A very clean and elegant UI and Ux used.

Very linear allowed features in free plan.

It is just best to use

Keeps track of my system logs and info, and saves me costs. Yes, am benefiting financially and very productive.

Intuitive user interface; helpful support (even on lower tiers); terraform support

Logs sometimes lag a little behind (although that might be caused by Heroku from where we are ingesting logs)

Visibility in all application logs

board and the screens, I really love how I can see what happened day to day. Really nice to be able to see the patterns and see where the spikes are coming from

Not that much that I do not like about LogDNA. There is too much good things to make something really stand out to you that is a bad thing for LogDNA. Its truly a great tool

Get it, its worth it.

With my team we are able to get alerts from the errors before the users reach out to us to let us know about the error. I love I know before they do and can have the issue fixed sometimes before they reach out.

LogDNA offers very affordable lower-tier plans, which is critical for a small project like mine. The availability of a Heroku Add-on and CloudWatch integration made it easy to get all my logs in one place.

The CloudWatch integration is a Lambda you must deploy yourself. The source for it had some issues that I had to work out myself, but LogDNA's Support team was responsive.

I use LogDNA to bring logs from different services on different cloud providers (Heroku, AWS) into one place for search and analytics. The Charts feature is great for getting base-level app metrics without having to build anything besides logging.

Two things:

- Being able to find and filter fast.

- Charting and trending data. You can identify an issue that is trending quickly. If you start throwing a lot of specific errors and they are trending, you can visually see you have a problem.

We've had some issues when we redeploy our kubernete containers. But, the team is working on solving that.

A few things.

- Monitoring for issues

- Identifying what endpoints are being used most, which helps us identify features in our apps that are possibly underutlized