-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add error.type field #566
Add error.type field #566
Conversation
schemas/error.yml
Outdated
@@ -29,6 +29,12 @@ | |||
description: > | |||
Error code describing the error. | |||
|
|||
- name: type | |||
level: core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kind of agree that this should be core but in general I would try to have as little field as possible in core as we will not get them "out there" anymore :-) Could we make it extended for now?
- name: type | ||
level: core | ||
type: keyword | ||
description: > |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add an example under example
key? Would also be great to have at least 2 examples in the description. The reason I'm insisting on this is that type
fields are always these "well we could fit everything in here" and its always hard to explain what is in. Having example should help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added an example
field but could not come up with a good second example for the description
At first I tried to map the exception class name to error.code.
But I don't think that's the best place for that.
In APM we also have both a code and a type for an exception.