# What are some ways to instrument scripts? **URL:** \ **Category:** Ignition\ **Tags:** perspective, vision, scripting\ **Created:** [May 19, 2023, 1:25pm UTC](https://forum.inductiveautomation.com/t/what-are-some-ways-to-instrument-scripts/73949 "2023-05-19T13:25:27Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [May 19, 2023, 2:09pm UTC](https://forum.inductiveautomation.com/t/what-are-some-ways-to-instrument-scripts/73949/3 "2023-05-19T14:09:22Z")
I also use b + f for most everything. When using scripts in perspective on components or in script transforms I use `system.perspective.print()`. I'm not sure if that's what you meant by "print" or if you meant the python built in print. A good reference for how "print" works in all of Ignition. > [@Event Configuration Print Out to debug](https://forum.inductiveautomation.com/t/event-configuration-print-out-to-debug/60091/5): > > It’s complicated slight_smile Starting from most local to least… In the script console, print will log directly to the output buffer on the right hand side. system.util.getLogger() will log to the named ‘Output Console’ Designer window. Bonus: A script invoked from here using system.util.invokeAsync will print to the regular output console, not the buffer on the right hand side. Anywhere else in the designer (except Perspective), print and system.util.getLogger will log to the ‘Out… --- _[View the full topic](https://forum.inductiveautomation.com/t/what-are-some-ways-to-instrument-scripts/73949)._