# Increase Project "Details" log period

**URL:** <https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149>\
**Category:** Ignition\
**Created:** [March 7, 2019, 11:29pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149 "2019-03-07T23:29:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [March 7, 2019, 11:29pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/1 "2019-03-07T23:29:07Z")

</div>

Is it possible to extend out the Project ‘details’ log so that log entries stay there for longer than 2 weeks?  
Is it also possible to query this table from elsewhere? This would be a great auditing tool, but if it can only be viewed from the webpage and only stores 2 weeks, it’s not all that useful.

E.g. this page in the Config web page under Projects → Details:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/f82d45ebd1bcdfa629d9691a536c0270e3034a4f.png)

---

<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 7, 2019, 11:39pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/2 "2019-03-07T23:39:37Z")

</div>

Well, this page is actually (temporarily) gone in 8.0, but we do have plans to bring it back and expose that kind of information in a more useful way. In 7.9, it’s just a separate table in the internal database, where we store a fairly coarse list. It’s capped so that it doesn’t overflow your internal DB.

We’ve also had some internal thoughts lately on how to expose project changes to the auditing system, which I think would also accomplish what you’re looking for here.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [March 7, 2019, 11:40pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/3 "2019-03-07T23:40:42Z")

</div>

Awesome, that sounds great 🙂

---

<div class="post-metadata">

**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\
**Post date:** [November 15, 2019, 9:39am UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/4 "2019-11-15T09:39:27Z")

</div>

> [@nminchin](#):
>
> Is it also possible to query this table from elsewhere? This would be a great auditing tool, but if it can only be viewed from the webpage and only stores 2 weeks, it’s not all that useful.

Hop this feature is incorporated in Ignition 8. Please advise, how can we access this change log information for project.

---

<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:** [November 15, 2019, 4:26pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/5 "2019-11-15T16:26:27Z")

</div>

We’re (I’m) actively working on adding project changes to the audit log, in a more granular way that would let you retrieve the same information that was previously in the project changes table.

---

<div class="post-metadata">

**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\
**Post date:** [November 16, 2019, 6:46am UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/6 "2019-11-16T06:46:06Z")

</div>

Thanks 👍

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [November 17, 2019, 1:42pm UTC](https://forum.inductiveautomation.com/t/increase-project-details-log-period/23149/7 "2019-11-17T13:42:09Z")

</div>

IMO it could be interesting to add Another audit table for project change and keep the original table for command with a foreign Key to the New table.  
Same way like the alarm table for associated data.
