# Put confd server in debug mode

**URL:** <https://dmap-community.ductus.global/t/put-confd-server-in-debug-mode/826>\
**Category:** Core Engine and APIs\
**Created:** [November 9, 2016, 4:02pm UTC](https://dmap-community.ductus.global/t/put-confd-server-in-debug-mode/826 "2016-11-09T16:02:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![issam](https://avatars.discourse-cdn.com/v4/letter/i/f05b48/32.png) [@issam](https://dmap-community.ductus.global/u/issam)\
**Post date:** [November 9, 2016, 4:02pm UTC](https://dmap-community.ductus.global/t/put-confd-server-in-debug-mode/826/1 "2016-11-09T16:02:11Z")

</div>

Hello,  
I need to sniff communication between application and the confd server any way to do it ?  
I think that some extrat argument must be added to confd command inorder to get log output.

Thanks !

---

<div class="post-metadata">

**Author:** ![jjohansson](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jjohansson](https://dmap-community.ductus.global/u/jjohansson)\
**Post date:** [November 9, 2016, 4:20pm UTC](https://dmap-community.ductus.global/t/put-confd-server-in-debug-mode/826/2 "2016-11-09T16:20:53Z")

</div>

Set the third argument to confd\_init() to CONFD\_PROTO\_TRACE like this:

`confd_init(argv[0], stderr, CONFD_PROTO_TRACE);`

CONFD\_TRACE instead of CONFD\_PROTO\_TRACE gives slightly less information.

The extra flags to confd you think about is: `confd --verbose --foreground ...`