# \[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:** 4

<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 6, 2026, 5:44pm UTC](https://forum.inductiveautomation.com/t/ign-7976-path-to-component-event/114353/4 "2026-03-06T17:44:17Z")

</div>

> [@\[IGN-7976\]Get Name of Message Handler Programmatically](https://forum.inductiveautomation.com/t/ign-7976-get-name-of-message-handler-programmatically/75750/2):
>
> No, this isn't directly possible. I wouldn't necessarily recommend going this route, but if you really wanted to, you can peek at the stack and find the 'filename' we feed into the Jython interpreter, which includes the handler name, which you could parse: def handleMessage(payload): import sys filename = sys.\_getframe().f\_code.co\_filename # ex: \<MessageHandlerScript:projectName/handlerName \> I'll make a note to consider adding the handler name to this somehow. It'd be nice.

This is basically the same request as this other post. There's an existing ticket (that I was unfortunately able to get done in 8.3.0) to add this kind of meta information, which is very easy for us to do, and very awkward for you to obtain) to scripts invoked as extension functions, via the ` __name__ ` or ` __file__ ` builtin keys.

---

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