-
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
[processor/servicegraphprocessor] Add Configurable Database Name Attribute #30726
[processor/servicegraphprocessor] Add Configurable Database Name Attribute #30726
Conversation
Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com>
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
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. Thanks!
@hadesy, once this is rebased, I'll do a final review and merge this. |
# Conflicts: # processor/servicegraphprocessor/README.md # processor/servicegraphprocessor/config_test.go # processor/servicegraphprocessor/testdata/service-graph-config.yaml
Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com>
…e' into add-configurable-dbname-attribute
Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com>
I've completed the rebase as requested. Everything should be in order now for the final review. Please let me know if there are any additional adjustments or checks needed from my side. Thank you for your guidance and support. Looking forward to the merge! |
Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com>
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
…ibute (open-telemetry#30726) **Description:** This PR introduces a new configuration option, 'database_name_attribute', in the ServiceGraphProcessor's Config struct. The purpose of this change is to allow users to specify a custom attribute name for identifying the database name in span attributes. This enhancement increases the flexibility of the servicegraphprocessor and allows for better customization in diverse deployment environments. The default value is set to 'db.name' to ensure backward compatibility. **Documentation:** - Updated the README.md to include the new configuration option, with an explanation and the default setting. - Added comments in the code where relevant to clarify the use and default value of the 'database_name_attribute'. --------- Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com> Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
…ibute (open-telemetry#30726) **Description:** This PR introduces a new configuration option, 'database_name_attribute', in the ServiceGraphProcessor's Config struct. The purpose of this change is to allow users to specify a custom attribute name for identifying the database name in span attributes. This enhancement increases the flexibility of the servicegraphprocessor and allows for better customization in diverse deployment environments. The default value is set to 'db.name' to ensure backward compatibility. **Documentation:** - Updated the README.md to include the new configuration option, with an explanation and the default setting. - Added comments in the code where relevant to clarify the use and default value of the 'database_name_attribute'. --------- Signed-off-by: hadesy <6346047+hadesy@users.noreply.github.com> Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Description:
This PR introduces a new configuration option, 'database_name_attribute', in the ServiceGraphProcessor's Config struct. The purpose of this change is to allow users to specify a custom attribute name for identifying the database name in span attributes. This enhancement increases the flexibility of the servicegraphprocessor and allows for better customization in diverse deployment environments. The default value is set to 'db.name' to ensure backward compatibility.
Documentation: