# Alarm Journal CSV export

**URL:** <https://forum.inductiveautomation.com/t/alarm-journal-csv-export/58100>\
**Category:** Ignition\
**Tags:** ignition81, vision, scripting\
**Created:** [April 6, 2022, 11:46am UTC](https://forum.inductiveautomation.com/t/alarm-journal-csv-export/58100 "2022-04-06T11:46:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [April 6, 2022, 4:06pm UTC](https://forum.inductiveautomation.com/t/alarm-journal-csv-export/58100/2 "2022-04-06T16:06:16Z")

</div>

The right way to do it would be to issue your own `system.alarm.queryJournal` call to match the filters on the component, which gives you access to the same underlying data.

The more efficient, but not directly supported way, would be to get a reference to the underlying table component inside the AJT component, then extract it’s model, which will have a `getAlarmAt(row)` field (and `getRowCount()` method), which would give you full access to the reconstructed alarm event and allow you to pull whatever data you want into your constructed CSV.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-journal-csv-export/58100)._