# Application level logging in a trigger

**URL:** <https://forum.canton.network/t/application-level-logging-in-a-trigger/4813>\
**Category:** App Development\
**Tags:** trigger\
**Created:** [June 30, 2022, 4:26am UTC](https://forum.canton.network/t/application-level-logging-in-a-trigger/4813 "2022-06-30T04:26:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Leonid\_Rozenberg](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/leonid_rozenberg/32/48_2.png) [@Leonid\_Rozenberg](https://forum.canton.network/u/Leonid_Rozenberg)\
**Post date:** [July 1, 2022, 4:48pm UTC](https://forum.canton.network/t/application-level-logging-in-a-trigger/4813/3 "2022-07-01T16:48:15Z")

</div>

Yes, they do!

> 12:37:16.598 [TriggerService-akka.actor.default-dispatcher-14] DEBUG daml.tracelog - [unknown source]: "Debug message from TriggerA"

adding

```xml
    <logger name="daml.tracelog" level="DEBUG">
        <appender-ref ref="STDOUT"/>
    </logger>

```

to the `trigger-service-logback.xml` file, and reverting the default level to `INFO`, does the trick.

---

_[View the full topic](https://forum.canton.network/t/application-level-logging-in-a-trigger/4813)._