# Good\_Overload results in excessive historian logging

**URL:** <https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571>\
**Category:** Ignition\
**Created:** [July 19, 2023, 9:25am UTC](https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571 "2023-07-19T09:25:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thijs1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/thijs1/32/14793_2.png) [@thijs1](https://forum.inductiveautomation.com/u/thijs1)\
**Post date:** [July 19, 2023, 9:25am UTC](https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571/1 "2023-07-19T09:25:07Z")

</div>

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

---

<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 19, 2023, 12:53pm UTC](https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571/2 "2023-07-19T12:53:05Z")

</div>

Two possibilities right off the top:

- Make expression tags with `forceQuality()` to strip out the bad quality, and historize those instead.

- Fix the overload on the drivers involved.

---

<div class="post-metadata">

**Author:** ![thijs1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/thijs1/32/14793_2.png) [@thijs1](https://forum.inductiveautomation.com/u/thijs1)\
**Post date:** [July 19, 2023, 1:09pm UTC](https://forum.inductiveautomation.com/t/good-overload-results-in-excessive-historian-logging/76571/3 "2023-07-19T13:09:38Z")

</div>

Ok, forceQuality() seems like a good solution. I will test this. Thanks Phill !