-
Notifications
You must be signed in to change notification settings - Fork 16
Mobile crash support #191
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
Mobile crash support #191
Conversation
package to get reused
|
@felixbarny, @kruskall - Thank you for your first review. I've updated the PR to address your suggestions, it should be all good now. Please take another look. |
|
I didn't do a full review but the thing I commented on is resolved, thanks! |
…lemetry-lib into mobile-crash-support
gregkalapos
left a comment
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.
The merge&resolving conflict looks ok to me. Sorry that my PR caused this.
elasticattr/attributes.go
Outdated
| ErrorType = "error.type" | ||
| ) | ||
|
|
||
| func GetTimestampUs(ts pcommon.Timestamp) int64 { |
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.
this adds a dependency on collector/pdata to the elasticattr package. If downstream consumer are using this package (without any other package using collector) they will bring in the extra dependency.
Can we move this out ?
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.
Sure. I just made the changes.
Fixes https://github.com/elastic/opentelemetry-dev/issues/831
Adds log crash event support by adding the following attributes to the logs with the
event.nameattribute or eventName field value set todevice.crash:The above attributes, along with the exception.* ones that come from the OTel conventions and should already be present on these kinds of logs, are what Kibana queries to properly display mobile crash events.
NOTE: Some of the logic needed for this to work was already present for traces, such as setting the
agent.nameresource attribute for example. To avoid duplicating code, I moved the common tools to a "common" dir.