# Audit Log Profile issue with too much data, remove some tags from logging **URL:** \ **Category:** Ignition\ **Created:** [October 18, 2022, 3:04am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324 "2022-10-18T03:04:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Matthew\_Brady](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Matthew\_Brady](https://forum.inductiveautomation.com/u/Matthew_Brady)\ **Post date:** [October 18, 2022, 3:04am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/1 "2022-10-18T03:04:11Z")
Hi, I have setup an audit profile, and enabled audit logging in the project, my only issue is we have some analog variables that are being logged about 10times a second due to changing values. I would just like a way to disable logging for some of these 'nuisance' variables, or a way to limit their logging. Ideally all we really want to log is when a user changes a variable from the SCADA interface. If there is a way to do this, could someone please direct me to where I can read up on it? Cheers, Matt ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [October 18, 2022, 3:06am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/2 "2022-10-18T03:06:55Z")
What version of Ignition are you running? ---
**Author:** ![Matthew\_Brady](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Matthew\_Brady](https://forum.inductiveautomation.com/u/Matthew_Brady)\ **Post date:** [October 18, 2022, 3:08am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/3 "2022-10-18T03:08:19Z")
Hi, Using version 7.9.10 ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [October 18, 2022, 3:10am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/4 "2022-10-18T03:10:29Z")
Interesting.. Are the analog values in question being written from logic within the Vision project itself? Or are they simply values being read in from a PLC? EDIT: I can imagine some situations where certain binding configurations might be trying to propagate writes back out to a tag and might end up in the audit profile.. In this case you might just need to adjust/correct things.. Normally the audit profile will capture just what you're wanting it to--values written/changed from a Vision client session. ---
**Author:** ![Matthew\_Brady](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Matthew\_Brady](https://forum.inductiveautomation.com/u/Matthew_Brady)\ **Post date:** [October 18, 2022, 3:37am UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/5 "2022-10-18T03:37:06Z")
The value is calculated in ignition from a table and then sent back to the PLC. Is there a way to stop logging of this tag? Yeah it is writing to a tag in the PLC. ---
**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:** [October 18, 2022, 12:34pm UTC](https://forum.inductiveautomation.com/t/audit-log-profile-issue-with-too-much-data-remove-some-tags-from-logging/65324/6 "2022-10-18T12:34:08Z")
> [@Matthew\_Brady](#): > > The value is calculated in ignition from a table You mean a table in a user interface? If so, no, you can't stop it. That's exactly what it is supposed to capture. Such continuous process tasks should be in a gateway timer event or other place independent of the UI. Clients do crash and/or get turned off, after all. Moving the process logic would make your system more robust and also get rid of the nuisance audit logs.