Why is screen-scraping Instana dashboards a poor foundation for automation?
Select an answer to reveal the explanation.
Short Explanation
You shouldn't build automation on a screen-scraped dashboard because the rendered interface isn't a stable contract. A layout change can silently break it or return wrong values. Use the documented API instead.
Full Explanation
The rendered interface is not a stable contract, so automation built on screen-scraped dashboards is fragile. Interfaces are designed for people and can change without notice, and the failure mode is often silent: a moved element can yield a plausible but incorrect number. The claim that dashboards render too slowly for automated collection is incorrect because speed is a minor concern next to correctness. The claim that scraping requires an API token in addition to a browser session is incorrect because scraping typically avoids tokens, which is part of the problem. The claim that dashboard values are rounded and therefore always inaccurate is incorrect because display formatting is not the main objection; interface instability is. For the exam, prefer the documented API over the presentation layer.