# Change logger defaults?

**URL:** <https://forum.inductiveautomation.com/t/change-logger-defaults/45419>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 9, 2021, 6:50am UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419 "2021-04-09T06:50:56Z")\
**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:** [April 9, 2021, 6:50am UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/1 "2021-04-09T06:50:56Z")

</div>

Is it possible to change the default state of a logger?

We have the Seeq module installed (0.46.2 (b0)) and by default, its `com.seeq.link.agent.DefaultAgent` and `com.seeq.link.agent.DefaultAgentKeyReader` loggers are set to DEBUG by default and are spamming our log file every 10 seconds with useless crap (below). I keep changing them to ‘INFO’, but obviously people keep pressing the “to defaults” button and it resets this each time 😕

Can I stop this?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/7/b7592be7192abaab1253b280ddeb99e59cf88332.png)

---

<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:** [April 9, 2021, 11:34am UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/2 "2021-04-09T11:34:35Z")

</div>

That will have to be fixed by Seeq. Because it must be a deliberate override in their module startup. Should not have been published like that… it violates IA’s module guidelines for loggers:

[https://docs.inductiveautomation.com/display/SE/Key+Design+Concepts](https://docs.inductiveautomation.com/display/SE/Key+Design+Concepts)

---

<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:** [April 9, 2021, 11:37am UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/3 "2021-04-09T11:37:07Z")

</div>

I figured that would be the case… ☹ I guess I’ll get in contact with them, cheers

---

<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:** [April 9, 2021, 4:30pm UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/4 "2021-04-09T16:30:41Z")

</div>

In the meantime, you can try to manually override, although this may still be overridden by the module's code:

> [@Logging level persistence](http://forum.inductiveautomation.com/t/logging-level-persistence/42232/2):
>
> If you get the exact name of your logger, you can add it to the logback.xml file in the gateway’s data/ directory - see this commented out line for the pattern to follow: \<!--\<logger name="example.logger" level="TRACE"/\>--\>

---

<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:** [April 29, 2021, 2:25am UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/5 "2021-04-29T02:25:55Z")

</div>

Their support actually said to use this way as well.

This is in their KB:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/7/67ff3a59c2cdede6bc622c866e4829d3db747ba9.png)

Then they step through manually overriding the level via that xml file, but with this note:  
**You must be using Seeq Ignition Module R50.4.3 or later.**

We’re using R22.46.02 😕

So that’s just a little frustrating… why would they set a useless logger to DEBUG. I literally have 500 pages with 95+% just those logs every time the server is rebooted and the person doesn’t turn this crap off…

---

<div class="post-metadata">

**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:** [April 29, 2021, 4:42pm UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/6 "2021-04-29T16:42:22Z")

</div>

I’ve had good luck recently driving enablement of DEBUG level against specific loggers via the [system.util.setLoggingLevel()](https://docs.inductiveautomation.com/display/DOC81/system.util.setLoggingLevel) function in a Gateway Startup script. I imagine you could use this to drop those loggers down as well on startup. This might be a little easier than hacking at the `logback.xml`.

---

<div class="post-metadata">

**Author:** ![JamesPD](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@JamesPD](https://forum.inductiveautomation.com/u/JamesPD)\
**Post date:** [July 24, 2024, 10:19pm UTC](https://forum.inductiveautomation.com/t/change-logger-defaults/45419/7 "2024-07-24T22:19:01Z")

</div>

Just a note here to say that Seeq now sets the logging level to INFO by default and persists the level across gateway restarts. Cheers!