Editor/IDE tooling for authoring OTTL — does it exist, any plans around it?

[srikar-kompella]

Hi all,

I've been writing a fair amount of OTTL lately (transform + filter processors) and keep hitting the same authoring friction: a small path typo or wrong function silently no-ops or only surfaces at collector runtime. Today the feedback loop is the web validators (ottl.run, Elastic's OTTL Playground), which are great but live outside the editor and the config files I'm actually working in.

Before I consider building anything, I wanted to check with the people closest to OTTL:

1. Does any editor/IDE tooling already exist for OTTL (syntax highlighting, path/function validation, a local dry-run)? I couldn't find a VS Code extension or language server — only the web playgrounds. Happy to be pointed at prior art I missed.
2. Is editor tooling intentionally out of scope, or just unowned? I read the OTTL roadmap ([pkg/ottl] OpenTelemetry Transformation Language and Transform Processor Roadmap #18643) — it's focused on processor consolidation and the declarative-syntax direction ([processor/transform] Add option to define OTTL with declarative syntax #11852), and I didn't see authoring/IDE tooling mentioned either way.
3. Would the community welcome a contributor-built VS Code extension along the lines of: highlighting → static lint of common errors (unknown functions, bad paths, malformed where) → eventually an offline dry-run that runs the real OTTL engine (compiled to Wasm) against sample telemetry in-editor? And is there any appetite to house something like that under the OTel umbrella down the line, or is it better kept as a community extension?
4. Would the planned declarative-syntax option ([processor/transform] Add option to define OTTL with declarative syntax #11852) change how editor tooling should be designed — i.e., should authoring tools target the statement grammar, the declarative form, or both? Trying not to build something the roadmap is about to reshape.

I've got Go + TypeScript background and am willing to do the work properly (track the grammar, not hard-code it). Mostly want to make sure I'd be filling a real gap and building it in a way maintainers would actually want. Thanks for any steer.