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

[connector/signaltometrics]Drop get OTTL func in favor of OTTL's ParseValueExpression #38101

Merged
merged 8 commits into from
Mar 3, 2025

Conversation

lahsivjar
Copy link
Member

Description

The component was using an internal get OTTL function as a stop gap measure to extract value from OTTL expressions due to lack of such function from the core OTTL library. With #35621, support for data extraction using OTTL value expressions was introduced. This PR uses the ParseValueExpression method and drops the get OTTL function. The function was documented in README as internal function and strictly advised not to be used in configurations so I don't expect any issues.

Link to tracking issue

Fixes #38098

Testing

Unit tests are passing

Documentation

README is updated

@andrzej-stencel andrzej-stencel merged commit d51d861 into open-telemetry:main Mar 3, 2025
156 checks passed
@github-actions github-actions bot added this to the next release milestone Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sunset the temporary get OTTL func in favour of ValueExpression support in the OTTL package
3 participants