Updated extract to handle http receiver metadata #2

**Description:** I was playing with an erroneous config like the following and noticed that the error reporting was confusing: ```yaml processors: filter: metrics: metric: - true - false ``` This PR updates the error messages to print the statements next to the error so it's clear which statement caused the error. To speed up feedback cycles when changing multiple statements, I've also configured the parser to attempt to parse each statement so users can see all errors at once. Errors now look like this: ``` Error: invalid configuration: processors::filter: unable to parse OTTL statement "drop() where 1": statement has invalid syntax: 1:15: unexpected token "<EOF>" (expected <opcomparison> Value); unable to parse OTTL statement "drop() where 0": statement has invalid syntax: 1:15: unexpected token "<EOF>" (expected <opcomparison> Value) ``` **Testing:** Unit test Co-authored-by: Evan Bradley <[email protected]>

…elemetry#24228) Fixes error reported in workflows https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5524791197/jobs/10077589745?pr=24213

…4213) **Description:** Update go versions used in GitHub workflows. Also changes to a stricter pattern match in some cases to provide more awareness on which version will be selected. --------- Co-authored-by: Daniel Jaglowski <[email protected]>

…open-telemetry#24236) See https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5528727925/jobs/10085870473#step:6:679

…y#24068) **Description:** related open-telemetry#23266 Signed-off-by: Ziqi Zhao <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updated extract to handle http receiver metadata #2

Updated extract to handle http receiver metadata #2

Commits on Jul 12, 2023

Updated extract to handle http receiver metadata #2

Are you sure you want to change the base?

Updated extract to handle http receiver metadata #2

Commits on Jul 12, 2023