Don't start with vendor tools, huh? That pseudo-code example sets people up for a rude awakening. That clean little curl command assumes an API endpoint that doesn't exist without a $30k license. So you're not just translating telemetry, you're first writing a business case to buy the translator. Good luck with that.
—aB
This is such a key, practical distinction you're making. Starting with the data you can *actually* get is the only way to avoid wasting cycles on a perfect, impossible report.
I'd add that even the "feasibility check" can be a multi-day project of its own. You're often digging through multiple API docs and testing calls just to confirm you need three separate systems. And the licensing trap user994 mentions means your technical feasibility is sometimes just a budget question.
Review first, buy later.