LogoLogo
  • Technical Direction
  • Technical overview
    • Technical Implementation
    • API Design Guide
      • Data Definitions and Standards
      • Data Transfer Objects
      • Documentation
      • Environments
      • Error Handling
      • Example API Service
      • GraphQL Naming Conventions
      • Methods
      • Naming Conventions
      • Once Only Principle
      • Pagination
      • Resource Oriented Design
      • REST Request
      • REST Response
      • Security
      • Versioning
    • Ísland.is Public Web Data Flow
    • Code Reviews
    • Code Standards
    • Monorepo
    • Project Management
    • Teamwork
    • Architectural Decision Records
      • Use Markdown Architectural Decision Records
      • Use NX
      • Continuous Integration
      • CSS
      • Branching and Release Strategy
      • Error Tracking and Monitoring
      • What API Management Tool to Consider
      • Viskuausan Static Site Generator
      • Use OAuth 2.0 and OpenID Connect As Protocols for Authentication and Authorization
      • Unified Naming Strategy for Files and Directories
      • CMS
      • Open Source License
      • What Chart Library Should We Use Across Island.is?
      • What Feature Flag Service/application Should We Use at Island.is?
      • Logging, Monitoring and APM Platform
      • ADR Template
    • Log Management Policy
  • Products
    • Island.is Authentication Service
      • Terminology
      • Integration Options
      • Authentication Flows
      • Authorising API Endpoints
      • Session Lifecycle
      • Scopes and Tokens
      • Delegations
      • Configuration
      • Tools and Examples
      • Environments
      • Test IAS with Postman
    • Notifications / Hnipp
      • New Notification Setup Guide
      • Notifications service workflow overview
      • Email notifications
    • Pósthólfið
      • Security Checklist
      • Introduction
      • Skjalatilkynning API
      • Skjalaveita API
      • Sequence Diagram
      • Interfaces
    • Straumurinn (X-Road)
      • Architecture Guidelines for Service Providers and Consumers
      • Setting up an X-Road Security Server
        • Network Configuration
      • X-Road - Uppfærsla á öryggisþjónum
      • Straumurinn - Notkun og umsýsla
      • X-Road Central - current version
  • Development
    • Getting Started
    • Generating a New Project
    • Definition of done
    • Devops
      • Continuous Delivery
      • Database
      • Dockerizing
      • Environment Setup
      • Logging
      • Metrics
      • NextJS Custom Server
      • Observability
      • Operations Base Principles
      • Security
      • Service Configuration
      • Support
    • AWS Secrets
    • Feature Flags
    • Documentation Contributions
    • Defining Monorepo Boundaries With Tags
    • OpenAPI
    • Code Generation
    • Workspace Settings (Deprecated)
    • External Contributions
  • REFERENCE
    • Problems
      • 400 Validation Failed
      • 400 Attempt Failed
      • 403 Bad Subject
      • 400 500 Template API Error
    • Glossary
  • Misc
    • Guide: Adding a Payment Step to an Application
    • Guide: Enable Organisations to Make Requests to an Application
    • README Template
Powered by GitBook
On this page
  • Context and Problem Statement
  • Considered Options
  • Decision Outcome
  • Pros and Cons of the Options
  • Bugsnag
  • Sentry

Was this helpful?

  1. Technical overview
  2. Architectural Decision Records

Error Tracking and Monitoring

PreviousBranching and Release StrategyNextWhat API Management Tool to Consider

Last updated 2 years ago

Was this helpful?

  • Status: accepted

  • Deciders: devs, devops

  • Date: 12.06.2020

Context and Problem Statement

Know it before they do! We need a tool to discover, triage, and prioritize errors in real-time.

Considered Options

Decision Outcome

Chosen option: Sentry, because it ranks higher in a community survey regarding our stack (Javascript). It's also much cheaper and offers the choice to be completely free if we self-host it.

Pros and Cons of the Options

Bugsnag

  • Good, because it offers a Slack integration for faster feedback.

  • Good, because it offers a Github integration to link to possible commits and PRs.

  • Good, because it offers bot front-side/server-side/serverless error tracking.

  • OK, because it was ranked the #5 as the best Javascript (client-side) error logging service in a community survey.

  • Bad, because it's expensive. ($199/mo for 450k events and 15 collaborators)

  • Bad, because it's pricing includes a fixed set of collaborators.

Sentry

  • Good, because it offers a Slack integration for faster feedback.

  • Good, because it offers a Github integration to link to possible commits and PRs.

  • Good, because it offers bot front-side/server-side/serverless error tracking.

  • Good, because it was ranked the #1 as the best Javascript (client-side) error logging service in a community survey.

  • Good, because it's cheaper than most error logging services out there (half the price of Bugsnag).

  • Good, because it offers the possibility of being completely free with a self-hosted solution (since Sentry is open-source).

  • Good, because you only pay for the number of events, regardless of how many collaborators.

  • Bad, because it costs (since we won't go with the self-hosted solution at first). ($89/mo for 500k events and ∞ collaborators)

Bugsnag
Sentry