# Knowing who tripped an alarm

**URL:** <https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528>\
**Category:** Ignition\
**Tags:** ignition81, perspective, scripting\
**Created:** [July 18, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528 "2023-07-18T16:13:49Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cameron\_Nickle](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@Cameron\_Nickle](https://forum.inductiveautomation.com/u/Cameron_Nickle)\
**Post date:** [July 18, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/1 "2023-07-18T16:13:49Z")

</div>

Hi all,

I'm currently working to see if there is a way to determine who is logged into a perspective session and trips an alarm on a tag (or if this is even possible). I'm doing this because I need this information later in my alarm pipeline to know who to send an email to about this alarm.

Thank you,

Cam

---

<div class="post-metadata">

**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:** [July 18, 2023, 4:35pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/2 "2023-07-18T16:35:15Z")

</div>

There is no direct way to associate a user with an alarm. There is an indirect way: use the audit system to track who writes to what in your process, providing a trail of events that could be examined for alarm correlations.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [July 18, 2023, 4:57pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/3 "2023-07-18T16:57:37Z")

</div>

If you're using a binding, there's no way to know who did it.

If you're setting the Tag value through scripting, then you could easily modify the script logic to write to your logs which user is making the write attempt.

```auto
def change_tag_value(tag_path, tag_value, username):
    # project script
    logger = system.util.getLogger("TAG_WRITE")
    logger.info("Tag write attempted. Path: {0} | Value: {1} | User: {2}".format(tag_path, tag_value, username))
    system.tag.writeBlocking([tag_path], [tag_value])

```

---

<div class="post-metadata">

**Author:** ![Cameron\_Nickle](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@Cameron\_Nickle](https://forum.inductiveautomation.com/u/Cameron_Nickle)\
**Post date:** [July 18, 2023, 5:44pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/4 "2023-07-18T17:44:34Z")

</div>

Well that is unfortunate that I cannot do it.

Are there any active requests to update the alarming system in relation to perspective? It would be very helpful if there was a way to send out an alarm through user properties in perspective and not have to go through the tagging system. The main reason being that the user properties are dynamic for each user and when you start using the tags you've changed the scope and now each user would have to fight over access to a single tags value.  
The main reason I want to do this is because for each given user I want to send out an alarm to a specific person if that users 'value' perspective property hits say 0.

Would this be possible to do in a later version of Ignition?

---

<div class="post-metadata">

**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:** [July 18, 2023, 6:06pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/5 "2023-07-18T18:06:25Z")

</div>

> [@Cameron\_Nickle](#):
>
> and not have to go through the tagging system

Alarming is fundamentally tied to tags, not client sessions. Which is why the auditing system is so useful when backtracking from alarms to potential user causes. Perhaps you should make a feature request, with specific details on how you would like it to work.

Related:

> [@Alarming in perspective via no tag or client tag or some other alertanive](https://forum.inductiveautomation.com/t/alarming-in-perspective-via-no-tag-or-client-tag-or-some-other-alertanive/75796):
>
> Hi all, I'm working on triggering my alarm pipeline from my perspective session. I've designed everything to be done through the session properties so each user has their own values of interest. The problem I am now facing is I have no tags, so I want to know if there is a way to set-off an alarm pipeline without a tag. (From what I've been reading this seem unlikely but I thought I'd ask) The more likely option is I will need a client tag to do this. I am wondering how I go about making a cli…

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 18, 2023, 6:07pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/6 "2023-07-18T18:07:29Z")

</div>

> [@Cameron\_Nickle](#):
>
> The main reason I want to do this is because for each given user I want to send out an alarm to a specific person if that users 'value' perspective property hits say 0.

Instead of pretending this is some kind of alarm can you just send them an email via scripting using `system.net.sendEmail`?

---

<div class="post-metadata">

**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:** [July 18, 2023, 6:10pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/7 "2023-07-18T18:10:02Z")

</div>

> [@Kevin.Herron](#):
>
> can you just send them an email via scripting

That's what came out of the other topic, too. 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![Cameron\_Nickle](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@Cameron\_Nickle](https://forum.inductiveautomation.com/u/Cameron_Nickle)\
**Post date:** [July 18, 2023, 6:10pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/8 "2023-07-18T18:10:46Z")

</div>

which other topic?

---

<div class="post-metadata">

**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:** [July 18, 2023, 6:12pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/9 "2023-07-18T18:12:03Z")

</div>

> [@Cameron\_Nickle](#):
>
> other topic?

The one I linked ~~five~~ _six_ minutes ago. It's one of **your** topics.

---

<div class="post-metadata">

**Author:** ![Cameron\_Nickle](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@Cameron\_Nickle](https://forum.inductiveautomation.com/u/Cameron_Nickle)\
**Post date:** [July 18, 2023, 6:17pm UTC](https://forum.inductiveautomation.com/t/knowing-who-tripped-an-alarm/76528/10 "2023-07-18T18:17:23Z")

</div>

Ohh, yeah I was focused on the props issue and forgot about that topic 😅,

Sorry @pturmel
