# Custom Logger tool to Filter Gateway Log Noise

**URL:** <https://forum.inductiveautomation.com/t/custom-logger-tool-to-filter-gateway-log-noise/117119>\
**Category:** General Discussion\
**Created:** [September 17, 2026, 4:15pm UTC](https://forum.inductiveautomation.com/t/custom-logger-tool-to-filter-gateway-log-noise/117119 "2026-09-17T16:15:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin.ayala](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@martin.ayala](https://forum.inductiveautomation.com/u/martin.ayala)\
**Post date:** [September 17, 2026, 4:15pm UTC](https://forum.inductiveautomation.com/t/custom-logger-tool-to-filter-gateway-log-noise/117119/1 "2026-09-17T16:15:11Z")

</div>

Brainstorm Feeler Post:

What are your experiences using custom loggers in your gateways and local projects?

Context:  
One issue that we have been having with our central gateway is a lot of nuisance log entries.

We are trying to figure out how to use [custom loggers](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-util/system-util-getLogger) to filter out these nuisance logs on the gateway.

The topics that we have to understand or ask are:

- What is a nuisance log entry and how will that be filtered (internal)

- Will filtered log entries save us gateway resources or just be visually hidden while still taking up resources

If I am misunderstanding the application or scope of custom loggers I would appreciate the feedback.

---

<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:** [September 17, 2026, 4:37pm UTC](https://forum.inductiveautomation.com/t/custom-logger-tool-to-filter-gateway-log-noise/117119/2 "2026-09-17T16:37:43Z")

</div>

Changing logging **levels** does impact logging resources. In scripting, you generally should use the `.debug()`, `.debugf()`, `.trace()`, and `.tracef()` methods to report potentially important information. These methods will short-circuit and avoid actually logging until a user sets the corresponding log level to DEBUG or TRACE. (All loggers start up in INFO level.)