# Obtaining Component Path on Mouse Click Event **URL:** \ **Category:** Ignition\ **Tags:** perspective, ignition81\ **Created:** [April 8, 2024, 6:12am UTC](https://forum.inductiveautomation.com/t/obtaining-component-path-on-mouse-click-event/88494 "2024-04-08T06:12:35Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 8, 2024, 12:21pm UTC](https://forum.inductiveautomation.com/t/obtaining-component-path-on-mouse-click-event/88494/4 "2024-04-08T12:21:18Z")
The component path is already encoded in logger keys when a logger is invoked within a component's scripts. See this discussion: > [@Component/View Path Syntax](https://forum.inductiveautomation.com/t/component-view-path-syntax/80412/2): > > Okay, bear with me... Given a stacktrace path of Experimentation/Repl@D$0:2:0:0/root/FlexContainer/Button: You can discern there was an error raised by the Experimentation/Repl View, in the Designer. There's no indication of which View this View is embedded wihtin, but from whichever View it is embedded within, the instance of the View is located along this path: 0:2:0:0. Note that anytime there is still a number remaining in the path that you should be looking for a container. Start at the… --- _[View the full topic](https://forum.inductiveautomation.com/t/obtaining-component-path-on-mouse-click-event/88494)._