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
Using the filter processor with an expression involving a comparison against an undefined symbol starting with an upper-case letter generates an error message the wording of which suggests a bug in the collector
Error: invalid configuration: processors::filter: unable to parse OTTL condition [...]: no value field set.
This is a bug in the OpenTelemetry Transformation Language
Steps to Reproduce
Run the collector with a filter comparing against an undefined symbol, such as value_double != NaN (NaN is undefined at the time of writing), value_int == IAmUndefined, or IAmUndefined == IAmUndefined.
Note that the behaviour is different for symbols not starting with upper-case letters (which generate either parsing errors or is not a valid path errors).
See attached config for full example.
Expected Result
Error message not indicating the error is a bug in the collector, such the one generated for lower-case symbols
[...] is not a valid path nor a valid OTTL keyword [...]
Error: invalid configuration: processors::filter: unable to parse OTTL condition "value_double != NaN": no value field set. This is a bug in the OpenTelemetry Transformation Language
2024/05/14 16:38:05 collector server run finished with error: invalid configuration: processors::filter: unable to parse OTTL condition "value_double != NaN": no value field set. This is a bug in the OpenTelemetry Transformation Language
Additional context
No response
The text was updated successfully, but these errors were encountered:
…33051)
**Description:**
Fix a bug where a condition like `"foo" = Bar` resulted in the error `no
value field set. This is a bug in the OpenTelemetry Transformation
Language`.
**Link to tracking Issue:** <Issue number if applicable>
Closes#33048
**Testing:** <Describe what testing was performed and which tests were
added.>
Updated unit tests
cparkins
pushed a commit
to AmadeusITGroup/opentelemetry-collector-contrib
that referenced
this issue
Jul 11, 2024
…pen-telemetry#33051)
**Description:**
Fix a bug where a condition like `"foo" = Bar` resulted in the error `no
value field set. This is a bug in the OpenTelemetry Transformation
Language`.
**Link to tracking Issue:** <Issue number if applicable>
Closesopen-telemetry#33048
**Testing:** <Describe what testing was performed and which tests were
added.>
Updated unit tests
Component(s)
processor/filter
What happened?
Description
Using the
filter
processor with an expression involving a comparison against an undefined symbol starting with an upper-case letter generates an error message the wording of which suggests a bug in the collectorSteps to Reproduce
Run the collector with a filter comparing against an undefined symbol, such as
value_double != NaN
(NaN
is undefined at the time of writing),value_int == IAmUndefined
, orIAmUndefined == IAmUndefined
.Note that the behaviour is different for symbols not starting with upper-case letters (which generate either parsing errors or
is not a valid path
errors).See attached config for full example.
Expected Result
Error message not indicating the error is a bug in the collector, such the one generated for lower-case symbols
or mixed case symbols
Actual Result
An error message indicating the issue is due to a bug in the collector
Collector version
v0.100.0
Environment information
Environment
Precompiled binary with md5sum
OS: Gentoo Linux
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: