Need advice about which tool to choose?Ask the StackShare community!
Add tool
Bugfender vs LogDNA: What are the differences?
Developers describe Bugfender as "Cloud logging for your apps, not only crashes matter". See the NSLogs of your customer applications remotely from your computer, it’s like having a remote Xcode console viewer. This way you can fix bugs easily. On the other hand, LogDNA is detailed as "Easy beautiful logging in the cloud". The easiest log management system you will ever use! LogDNA is a cloud-based log management system that allows engineering and devops to aggregate all system and application logs into one efficient platform. Save, store, tail and search app.
Bugfender and LogDNA belong to "Log Management" category of the tech stack.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Bugfender
Pros of LogDNA
Pros of Bugfender
- Crash reporting1
- Mobile exception tracking1
- Free1
- IOS1
- Android1
- Great UI1
- Great reports1
- Advanced Logging1
- GDPR1
Pros of LogDNA
- Easy setup6
- Cheap4
- Extremely fast3
- Powerful filtering and alerting functionality2
- Graphing capabilities1
- Export data to S31
- Multi-cloud1
Sign up to add or upvote prosMake informed product decisions
Cons of Bugfender
Cons of LogDNA
Cons of Bugfender
Be the first to leave a con
Cons of LogDNA
- Limited visualization capabilities1
- Cannot copy & paste text from visualization1
Sign up to add or upvote consMake informed product decisions
What is Bugfender?
See the NSLogs of your customer applications remotely from your computer, it’s like having a remote Xcode console viewer. This way you can fix bugs easily.
What is LogDNA?
The easiest log management system you will ever use! LogDNA is a cloud-based log management system that allows engineering and devops to aggregate all system and application logs into one efficient platform. Save, store, tail and search app
Need advice about which tool to choose?Ask the StackShare community!
What companies use Bugfender?
What companies use LogDNA?
What companies use Bugfender?
What companies use LogDNA?
See which teams inside your own company are using Bugfender or LogDNA.
Sign up for StackShare EnterpriseLearn MoreSign up to get full access to all the companiesMake informed product decisions
What tools integrate with Bugfender?
What tools integrate with LogDNA?
What tools integrate with LogDNA?
Blog Posts
+46 27
32614
What are some alternatives to Bugfender and LogDNA?
Bugsnag
Bugsnag captures errors from your web, mobile and back-end applications, providing instant visibility into user impact. Diagnostic data and tools are included to help your team prioritize, debug and fix exceptions fast.
Crashlytics
Instead of just showing you the stack trace, Crashlytics performs deep analysis of each and every thread. We de-prioritize lines that don't matter while highlighting the interesting ones. This makes reading stack traces easier, faster, and far more useful! Crashlytics' intelligent grouping can take 50,000 crashes, distill them down to 20 unique issues, and then tell you which 3 are the most important to fix.
Logstash
Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). If you store them in Elasticsearch, you can view and analyze them with Kibana.
SLF4J
It is a simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks allowing the end user to plug in the desired logging framework at deployment time.
Logback
It is intended as a successor to the popular log4j project. It is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks and logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality.