Skip to content
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

[otel-plugin] Add aliases for spanevent/logrecord exceptions #113636

Merged
merged 9 commits into from
Oct 2, 2024

Conversation

gregkalapos
Copy link
Contributor

@gregkalapos gregkalapos commented Sep 26, 2024

Adding aliases for exception fields.

@gregkalapos gregkalapos self-assigned this Sep 26, 2024
@elasticsearchmachine elasticsearchmachine added v9.0.0 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Sep 26, 2024
@gregkalapos
Copy link
Contributor Author

@elasticmachine update branch

@gregkalapos gregkalapos changed the title [otel-plugin] Covering spanevent/logrecord exceptions with tests [otel-plugin] Add aliases for spanevent/logrecord exceptions Oct 1, 2024
@gregkalapos gregkalapos marked this pull request as ready for review October 1, 2024 14:55
@gregkalapos gregkalapos requested a review from a team as a code owner October 1, 2024 14:55
@elasticsearchmachine elasticsearchmachine added the needs:triage Requires assignment of a team area label label Oct 1, 2024
error.exception.message:
type: alias
path: attributes.exception.message

Copy link
Contributor Author

@gregkalapos gregkalapos Oct 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No alias for handled, because we send it as error.exceptin.handled (by inverting exception.escaped and attaching it in the enrichment lib) - and that works via passthrough.

Just raising it here to double-check: that's ok, right?

@gregkalapos gregkalapos requested a review from felixbarny October 1, 2024 15:12
@gregkalapos gregkalapos added the :Data Management/Data streams Data streams and their lifecycles label Oct 1, 2024
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team and removed needs:triage Requires assignment of a team area label labels Oct 1, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Contributor

@lahsivjar lahsivjar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Do we need to bump the version too?

@gregkalapos
Copy link
Contributor Author

@elasticmachine update branch

@gregkalapos
Copy link
Contributor Author

LGTM! Do we need to bump the version too?

To be on the safe side, I increased it.

@gregkalapos
Copy link
Contributor Author

I think the failing test is being fixed in #113890.

@felixbarny
Copy link
Member

@elasticmachine update branch

@gregkalapos gregkalapos merged commit af7c81e into elastic:main Oct 2, 2024
16 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 113636

@gregkalapos
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

gregkalapos added a commit to gregkalapos/elasticsearch that referenced this pull request Oct 2, 2024
…#113636)

* Add tests for exceptions

* Adapt aliases and move into a separate file

* Clarify description in alias files

* Handling stacktrace

* Move error aliases to [email protected]

* Update resources.yaml

---------

Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit af7c81e)

# Conflicts:
#	x-pack/plugin/otel-data/src/main/resources/resources.yaml
elasticsearchmachine pushed a commit that referenced this pull request Oct 3, 2024
#113925)

* Add tests for exceptions

* Adapt aliases and move into a separate file

* Clarify description in alias files

* Handling stacktrace

* Move error aliases to [email protected]

* Update resources.yaml

---------

Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit af7c81e)

# Conflicts:
#	x-pack/plugin/otel-data/src/main/resources/resources.yaml

Co-authored-by: Felix Barnsteiner <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this pull request Oct 4, 2024
…#113636)

* Add tests for exceptions

* Adapt aliases and move into a separate file

* Clarify description in alias files

* Handling stacktrace

* Move error aliases to [email protected]

* Update resources.yaml

---------

Co-authored-by: Elastic Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport pending :Data Management/Data streams Data streams and their lifecycles external-contributor Pull request authored by a developer outside the Elasticsearch team >non-issue Team:Data Management Meta label for data/management team v8.16.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants