# Trigger service log level

**URL:** <https://forum.canton.network/t/trigger-service-log-level/3995>\
**Category:** App Development\
**Tags:** daml\
**Created:** [February 23, 2022, 9:48am UTC](https://forum.canton.network/t/trigger-service-log-level/3995 "2022-02-23T09:48:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shirana](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@shirana](https://forum.canton.network/u/shirana)\
**Post date:** [February 23, 2022, 9:48am UTC](https://forum.canton.network/t/trigger-service-log-level/3995/1 "2022-02-23T09:48:33Z")

</div>

I’m using trigger-service-1.18.0.jar and can see logs in DEBUG level.  
for example this secion in the code ( from trigger/Runner.scala file)  
`freeTriggerSubmits(clientTime, v = updateWithNewState) .leftMap( _.expect( "TriggerRule new state", { case DamlTuple2(SUnit, newState) => logger.debug(s"New state: $newState") newState }, ).orConverterException )`  
prints in DEBUG mode the content of the contract…  
How can that be avoided?  
How can I control the logging level of the service?

---

<div class="post-metadata">

**Author:** ![Stephen](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/stephen/32/102_2.png) [@Stephen](https://forum.canton.network/u/Stephen)\
**Post date:** [March 15, 2022, 9:57pm UTC](https://forum.canton.network/t/trigger-service-log-level/3995/2 "2022-03-15T21:57:50Z")

</div>

As this was a code issue, further discussion happened over on Daml issues, including both controlling log level and fixing the defaults for the trigger service jar:

> <https://github.com/digital-asset/daml/issues/13042>
>
> I’m using trigger-service-1.18.0.jar and can see logs in DEBUG level.
> for examp…le this secion in the code ( from trigger/Runner.scala file):
> 
> \`freeTriggerSubmits(clientTime, v = updateWithNewState) .leftMap( \_.expect( "TriggerRule new state", { case DamlTuple2(SUnit, newState) =\> logger.debug(s"New state: $newState") newState }, ).orConverterException )\`
> 
> prints in DEBUG mode the content of the contract.
> How can that be avoided?
> How can I control the logging level of the service?