You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a problem with incorrect telemetry sent by old versions of mobile application that I can't change or force to update. There is no way to distinguish this telemetry data other than by resource attribute "version". I found that OTTL which is used in the filter processor doesn't have semver version convertor and there is no other converter that can be used to parse and compare semver version from the attribute.
Describe the solution you'd like
Add semver version matcher into OTTL package that can convert the attribute value into semver version and compare it to the pattern specified as an argument: IsMatchVersion(resource.attributes["version"], "<1.2")
Describe alternatives you've considered
I didn't find any other way to solve it. A proactive solution to prevent this from happening again is to always provide a numeric version of the application along with a string version in resource attributes.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
I have a problem with incorrect telemetry sent by old versions of mobile application that I can't change or force to update. There is no way to distinguish this telemetry data other than by resource attribute "version". I found that OTTL which is used in the filter processor doesn't have semver version convertor and there is no other converter that can be used to parse and compare semver version from the attribute.
Describe the solution you'd like
Add semver version matcher into OTTL package that can convert the attribute value into semver version and compare it to the pattern specified as an argument:
IsMatchVersion(resource.attributes["version"], "<1.2")
Describe alternatives you've considered
I didn't find any other way to solve it. A proactive solution to prevent this from happening again is to always provide a numeric version of the application along with a string version in resource attributes.
Additional context
No response
The text was updated successfully, but these errors were encountered: