# Getting the Initial Value that Triggered an Alarm **URL:** \ **Category:** Ignition\ **Created:** [December 6, 2021, 10:43pm UTC](https://forum.inductiveautomation.com/t/getting-the-initial-value-that-triggered-an-alarm/53820 "2021-12-06T22:43:21Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [December 7, 2021, 5:27pm UTC](https://forum.inductiveautomation.com/t/getting-the-initial-value-that-triggered-an-alarm/53820/5 "2021-12-07T17:27:21Z")
It should be: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c4459eec776caba9effef8a023443136f6064cd.png) You could also call `sourceEvent()`; the `PyAlarmEvent` should then give you the underlying AlarmEvent directly. I'd recommend poking around at the event object via Phil Turmel's introspection script: > [@Finding all available methods from a component](https://forum.inductiveautomation.com/t/finding-all-available-methods-from-a-component/9670/8): > > The introspection script has evolved over time, particularly to return a string result instead of just printing. I found that useful for introspection in gateway scope using runScript() in an expression tag. Or to set the .text property of a scrollable text edit field for convenience. This is what it looks like today: # Introspection for Jython/Java # # Copyright 2008-2016 Automation Professionals, LLC \ # # Redistribution and use in source and binary forms, with or… --- _[View the full topic](https://forum.inductiveautomation.com/t/getting-the-initial-value-that-triggered-an-alarm/53820)._