-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 setStatus operation for spanprocessor #5886
Add setStatus operation for spanprocessor #5886
Conversation
Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
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.
Looking good, just one more thing to fix from my side
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.
LGTM
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.
Sorry, we need to finalize the transform processor configs before adding new functionality
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@bogdandrutu Are there any delivery estimates for that pre-requirement? |
Hi @bogdandrutu Could you please link corresponding issue that should be done first? |
Here is the design doc open-telemetry/opentelemetry-collector#4444 |
One more use-case for this PR is if somebody is unhappy with open-telemetry/opentelemetry-specification#1998, then using this new processor they can set status back to error |
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.
Because of the recent spec change we need this functionality before the stable transform processor is designed.
@TomRoSystems @iNikem fyi this functionality will be deprecated soon (and replace by the transform processor), so consider to not use it unless critical.
@bogdandrutu is there some description/issue/anything about this "transform processor"? |
+1, can we get some transparency to expected transform processor design and the any estimates on release date / deprecation date? There are several asks for the possibility to get the possibility for overriding the span status set by instrumentations and looking for guidance how to enable such use cases while taking the upgrade path into account @bogdandrutu |
@iNikem @ivomagi IIUC this is the design doc for that processor #5886 (comment) |
* Add setStatus operation for spanprocessor * Change code to have text format instead of numeric and add another example * Add "Unset" value and tests * Update README for Unset value * Apply suggestions from code review Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> * From review: Move statuses names to constants and fix "Err" => "Error" * Code review: fixing style * One more "Err" and fixing comment(s) as suggested from review * Clear status description for cases different than error Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
Description: Added possibility to change span status and description.
Link to tracking Issue: #4754
Testing: Added two unit tests in span_test.go
Documentation: Updated README inside spanprocessor and added two examples with comments in
config.yaml