Bugfender vs Logmatic vs Papertrail

Need advice about which tool to choose?Ask the StackShare community!

Bugfender

11
19
+ 1
9
Logmatic

68
77
+ 1
238
Papertrail

610
379
+ 1
273
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Bugfender
Pros of Logmatic
Pros of Papertrail
  • 1
    Crash reporting
  • 1
    Mobile exception tracking
  • 1
    Free
  • 1
    IOS
  • 1
    Android
  • 1
    Great UI
  • 1
    Great reports
  • 1
    Advanced Logging
  • 1
    GDPR
  • 35
    Powerful Data Vizualization
  • 31
    Live search
  • 30
    Super reactive interface
  • 28
    Amazing support team
  • 27
    Real-time alerts on slack
  • 24
    Easy setup
  • 22
    Performance
  • 20
    It's amazing
  • 17
    Just works. gracefully
  • 4
    Superb product. Helps us deliver great customer support
  • 85
    Log search
  • 43
    Easy log aggregation across multiple machines
  • 43
    Integrates with Heroku
  • 37
    Simple interface
  • 26
    Backup to S3
  • 19
    Easy setup, independent of existing logging setup
  • 15
    Heroku add-on
  • 3
    Command line interface
  • 1
    Alerting
  • 1
    Good for Startups

Sign up to add or upvote prosMake informed product decisions

Cons of Bugfender
Cons of Logmatic
Cons of Papertrail
    Be the first to leave a con
      Be the first to leave a con
      • 2
        Expensive
      • 1
        External Network Goes Down You Wont Be Logging

      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 Logmatic?

      Get a clear overview of what is happening across your distributed environments, and spot the needle in the haystack in no time. Build dynamic analyses and identify improvements for your software, your user experience and your business.

      What is Papertrail?

      Papertrail helps detect, resolve, and avoid infrastructure problems using log messages. Papertrail's practicality comes from our own experience as sysadmins, developers, and entrepreneurs.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Bugfender?
      What companies use Logmatic?
      What companies use Papertrail?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Bugfender?
      What tools integrate with Logmatic?
      What tools integrate with Papertrail?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      What are some alternatives to Bugfender, Logmatic, and Papertrail?
      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.
      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.
      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.
      See all alternatives