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

feat: add span events as an attribute called "events" #2886

Merged
merged 3 commits into from
Jul 7, 2023

Conversation

mathnogueira
Copy link
Member

This PR adds the structure for Span events. When present, they will be added to the attributes map as events.

Checklist

  • tested locally
  • added new dependencies
  • updated the docs
  • added a test

@mathnogueira mathnogueira changed the base branch from main to feat/support-span-events July 7, 2023 20:42
@mathnogueira mathnogueira merged commit a54f905 into feat/support-span-events Jul 7, 2023
25 checks passed
@mathnogueira mathnogueira deleted the feat/events-as-attributes branch July 7, 2023 20:44
mathnogueira added a commit that referenced this pull request Jul 11, 2023
* feat: add span events as an attribute called "events" (#2886)

* feat: add span events as an attribute called "events"

* update attribute name to "span.events"

* fix test

* feat: support events in Jaeger, Tempo, and all OTLP datastores (both gRPC and HTTP variants) (#2887)

support events in jaeger and tempo (grpc and http)

* feat: events app insights (#2905)

* feat: support span events in app insights

* don't ignore error and fix function names

* docs: span events (#2920)

* add docs and test in expression executor

* Update docs/docs/cli/creating-test-specifications.md

Co-authored-by: Julianne Fermi <julianne@kubeshop.io>

---------

Co-authored-by: Julianne Fermi <julianne@kubeshop.io>

---------

Co-authored-by: Julianne Fermi <julianne@kubeshop.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants