Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
GitLab Enterprise Edition
GitLab Enterprise Edition
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 2,406
    • Issues 2,406
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 201
    • Merge Requests 201
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Enterprise EditionGitLab Enterprise Edition
  • Issues
  • #5459

Closed
Open
Opened Sep 19, 2017 by Sid Sijbrandij@sytses 
  • Report abuse
  • New issue
Report abuse New issue

Error Tracking

Error Tracking allows GitLab to receive and act on application errors.

This would be an alternative to Sentry. As you can see on their site there is a lot of functionality that can go into this. But a minimum viable change would be:

  1. Create another service desk, but call it Error Tracking.
  2. When active it generates an email address: incoming+gitlab-org/gitlab-ce+errors@gitlab.com
  3. Emails that come in create an issue

Next step would be that similar errors are aggregated. But that doesn't need to be part of the initial product.

BTW Interesting to see that Sentry is integrating source code https://blog.sentry.io/2017/05/01/release-commits.html So it makes sense to combine source code and errors in the same application.

BTW2 If we start working with the AppSignal agent we can make collecting errors automatic instead of people having to configure it https://github.com/smartinez87/exception_notification#rails

Edited Apr 11, 2018 by Mark Pundsack

Related issues

Assignee
Assign to
Epic
Next 7-13 releases
Milestone
Next 7-13 releases
Assign milestone
Time tracking
None
Due date
No due date
8
Labels
CI/CD GitLab Ultimate Monitoring Product Vision 2018 devops:monitor direction error tracking feature proposal
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ee#5459