Feature #2241

An Error-mapping service should exist to provide better error-reporting

Added by Luke Kanies about 3 years ago. Updated about 1 year ago.

Status:Accepted Start date:05/11/2009
Priority:High Due date:
Assignee:Randall Hansen % Done:

0%
Category:plumbing
Target version:3.X
Affected Puppet version:0.24.8 Branch:
Keywords:usability
Votes: 0

Description

We often get errors from underlying classes that are essentially meaningless. We should have a simple exception-mapping service that converts these useless strings into more meaningful bits.

History

#1
Updated by Luke Kanies over 2 years ago

  • Assignee set to Rein Henrichs

#2
Updated by James Turnbull over 2 years ago

  • Target version changed from 2.6.0 to 2.7.x

#3
Updated by James Turnbull about 1 year ago

  • Status changed from Accepted to Needs Decision
  • Assignee changed from Rein Henrichs to Nigel Kersten

#4
Updated by Nigel Kersten about 1 year ago

  • Status changed from Needs Decision to Accepted
  • Assignee changed from Nigel Kersten to Randall Hansen
  • Priority changed from Normal to High
  • Target version changed from 2.7.x to 3.X

Randall, assigning to you for fleshing out more details, as this clearly impacts the user experience of the product.

#5
Updated by Nigel Kersten about 1 year ago

  • Keywords set to usability

#6
Updated by Luke Kanies about 1 year ago

Note that one of the goals here is that the errors could be used to look up external documentation, akin to how IBM uses error IDs, which can then be easily queried.

#7
Updated by Nigel Kersten about 1 year ago

Apple actually moved to this model with their DirectoryServices errors, but made the mistake of only ever reporting the error number in logs etc, which can get really frustrating, and led them to develop ‘dserr’ which looks up human-readable descriptions based on error numbers.

I’d like to see us be much more usable than that.

Also available in: Atom PDF