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.
Currently, when trying to convert a value from a float to string the only way I've seen to convert a number value to a string is to use the Concat function.
example parser using OTTL to convert a float into epoch time:
In the first set function, To ensure we can split on attributes["test"], with the value of 1234456.1234546, representing s.ms, we have to Call Concat to change it from a float to a string.
Describe the solution you'd like
A new function called String takes in a value and converts it into a string if possible.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
Currently, when trying to convert a value from a
float
tostring
the only way I've seen to convert a number value to a string is to use theConcat
function.example parser using OTTL to convert a float into epoch time:
In the first set function, To ensure we can split on
attributes["test"]
, with the value of1234456.1234546
, representings.ms
, we have to CallConcat
to change it from afloat
to astring
.Describe the solution you'd like
A new function called
String
takes in a value and converts it into a string if possible.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: