# \[IGN-7976\]Path to Component Event

**URL:** <https://forum.inductiveautomation.com/t/ign-7976-path-to-component-event/114353>\
**Category:** Ignition\
**Tags:** perspective, vision\
**Created:** [March 5, 2026, 11:06pm UTC](https://forum.inductiveautomation.com/t/ign-7976-path-to-component-event/114353 "2026-03-05T23:06:36Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 9, 2026, 4:48pm UTC](https://forum.inductiveautomation.com/t/ign-7976-path-to-component-event/114353/6 "2026-03-09T16:48:35Z")

</div>

Consider also exploring what you have access to through the MDC thread locals, which we use to decorate our logs:

> [@Can a Python script detect which Perspective view or binding it is running in?](https://forum.inductiveautomation.com/t/can-a-python-script-detect-which-perspective-view-or-binding-it-is-running-in/99937/3):
>
> Possibly a starting point here: If you just log (not print!) a message, you should get useful MDC output indicating some information. Technically you could retrieve that at runtime, via the static method on the MDC class: org.slf4j.MDC.get("key") As in: from org.slf4j import MDC component = MDC.get("component")

> [@Function Exception Logging: Capturing Source](https://forum.inductiveautomation.com/t/function-exception-logging-capturing-source/93156/6):
>
> Probably: In one thread: org.slf4j.MDC.getCopyOfContextMap() In the other thread: org.slf4j.MDC.setContextMap(map)

---

_[View the full topic](https://forum.inductiveautomation.com/t/ign-7976-path-to-component-event/114353)._