We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
limit
pkg/ottl
Collector terminated with an error when trying to use the OTTL limit function in a transform processor config.
0.77.0
Docker on Linux
receivers: otlp: protocols: http: processors: transform: log_statements: - context: resource statements: - limit(attributes, 1, []) exporters: logging: service: pipelines: logs: exporters: [logging] processors: [transform] receivers: [otlp]
Error: invalid configuration: processors::transform: undefined function limit 2023/05/15 09:50:09 collector server run finished with error: invalid configuration: processors::transform: undefined function limit
I think this is because #18822 accidentally set the factory name to uppercase, but functions in OTTL have to be lowercase. See:
opentelemetry-collector-contrib/pkg/ottl/ottlfuncs/func_limit.go
Line 33 in d67cbca
The text was updated successfully, but these errors were encountered:
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Component(s)
pkg/ottl
What happened?
Description
Collector terminated with an error when trying to use the OTTL
limit
function in a transform processor config.Collector version
0.77.0
Environment information
Docker on Linux
Environment
OpenTelemetry Collector configuration
Log output
Additional context
I think this is because #18822 accidentally set the factory name to uppercase, but functions in OTTL have to be lowercase. See:
opentelemetry-collector-contrib/pkg/ottl/ottlfuncs/func_limit.go
Line 33 in d67cbca
The text was updated successfully, but these errors were encountered: