# Configure boolean tag history

**URL:** <https://forum.inductiveautomation.com/t/configure-boolean-tag-history/92520>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 28, 2024, 7:59am UTC](https://forum.inductiveautomation.com/t/configure-boolean-tag-history/92520 "2024-06-28T07:59:13Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [June 28, 2024, 12:32pm UTC](https://forum.inductiveautomation.com/t/configure-boolean-tag-history/92520/5 "2024-06-28T12:32:40Z")

</div>

> [@Good\_Overload results in excessive historian logging](https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571):
>
> Hi, We are experiencing troubles with a customer that has excessive historian logging. I suspect the main reason are some tags who flip to Good\_Overload("Sampling has slowed down due to resource limitations.") Quality and then back to GOOD quality. I suspect this issues a historian change and makes the historian log this in our database. Strangly enough the log entry has status code 192. Is there a way to avoid this excessive logging? Thank you, Thijs Ignition Platform 8.1.12

---

_[View the full topic](https://forum.inductiveautomation.com/t/configure-boolean-tag-history/92520)._