-
Notifications
You must be signed in to change notification settings - Fork 18
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: Implement otel tracing hook. #130
Conversation
This PR should be reviewed before other hooks PRs. This PR adds supporting types for hooks, but does not use them from the client. --------- Co-authored-by: Casey Waldren <cwaldren@launchdarkly.com>
Second PR. This connects hooks to the ldclient. It does not add the `Ex` methods to any interface, and it does not add `AddHooks` to any interface. --------- Co-authored-by: Casey Waldren <cwaldren@launchdarkly.com>
…sts. (#131) This is a "chore" because I plan on rebase merging this feature branch and this is not a release-note change.
@@ -20,22 +20,38 @@ COVERAGE_ENFORCER_FLAGS=-package github.com/launchdarkly/go-server-sdk/v7 \ | |||
-skipcode "// COVERAGE" \ | |||
-packagestats -filestats -showcode | |||
|
|||
.PHONY: build clean test test-coverage benchmarks benchmark-allocs lint | |||
ALL_BUILD_TARGETS=sdk ldotel |
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.
Should we add the test service? It does not pass linting right now, because it doesn't seem to have accounted for the nested modules not working with ./...
.
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 am going with no. We can add it to linting later, but fixing all its lint problems will need a PR as well.
This PR should not be merged until after hooks have been released in a go-server-sdk version. |
Changed my mind and added things here. |
I think I have convinced myself to have 2 ci workflows though, and will do that here. Other monorepo tasks would be: |
Co-authored-by: Casey Waldren <cwaldren@launchdarkly.com>
Co-authored-by: Casey Waldren <cwaldren@launchdarkly.com>
🤖 I have created a release *beep* *boop* --- ## [7.4.0](v7.3.0...v7.4.0) (2024-04-10) This release contains no functional changes. It is a product of structural changes to the repository. ### Features * Implement otel tracing hook. ([#130](#130)) ([f5675c1](f5675c1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## 1.0.0 (2024-04-11) ### Features * Implement otel tracing hook. ([#130](#130)) ([f5675c1](f5675c1)) * Update to use go-server-sdk 7.4.0 ([#147](#147)) ([0603a9a](0603a9a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Adds the otel hook.
Adds a workspace.
Before using the workspace you need to: