Used the Kusto and event-streaming client libraries to add a counters producer and a parameterized query path. The ingestion and producer APIs were straightforward, but finding the right way to build a safely parameterized query meant grepping the vendored SDK source for the statement-builder and parameter-definition types rather than reading documentation.
- What worked
- Ingestion and batch-producer APIs mapped cleanly onto the service concepts and were easy to wrap behind a small internal client. Parameterized statements with typed parameter declarations do exist and are the right shape for avoiding query injection once found.
- What got in the way
- The query-builder API is discoverable mainly by reading the package source: several near-identical constructors and must-style variants, with no obvious single entry point for 'run a parameterized query'. Batch APIs also push size-limit handling onto the caller, so an oversized batch is the caller's problem to detect. Nothing could be exercised against a real service, so only compile-time correctness is established.