Is there a way to enable verbose logging, particularly for Directory Sync?

[DanHetheringtonIL]

TL;DR: Is there a way to turn on debug logging for Jackson, in particular to debug a connection problem in the sending of Directory Sync webhooks from Jackson to my app?

For more context, in case it's helpful:

I would like to use Jackson to handle only Directory Sync for users within my Rails app. For local development, I have set up Jackson (using image boxyhq/jackson:1.14.2), a postgres database (for Jackson) and my Rails app as separate Docker containers.

I have set up a skeleton SCIM endpoint within the Rails app, which I can access as expected from other containers within the stack.

I have configured Jackson to talk to a JumpCloud account via ngrok, which also seems to be working as expected: I can see the users in the Jackson admin portal in Directory Sync -> Connections -> JumpCloud -> Users tab.

However, when changes are synced over from JumpCloud to Jackson, the webhooks don't reach my app. My app has verbose logging enabled, so I am confident it is not receiving anything (including anything sent to an incorrect route). On the Jackson side, the only logs I see are along these lines:

mystack-jackson-1  | Retrying sending webhook event to my-app:3000/scim/webhook... Attempt 1
mystack-jackson-1  | Retrying sending webhook event to my-app:3000/scim/webhook... Attempt 2
mystack-jackson-1  | Retrying sending webhook event to my-app:3000/scim/webhook... Attempt 1

This URL (my-app...) is as expected. Is there any way to see more detailed information on what is happening here? (Or does anybody have a seasoned guess as to where I might be going wrong?)

[devkiran]

@DanHetheringtonIL Thanks for sharing the issue. There is no way to turn on debug logging for Jackson at the moment. I'll try to reproduce this issue and get back to you.

[deepakprabhakara]

@devkiran We should surface up the error in the Attempt log message to provide more context.

[DanHetheringtonIL]

I have resolved this now — I hadn't specified a protocol for the webhook endpoint. I don't know what Jackson was attempting or where the 500 responses were coming from. Maybe a dumb mistake, but a more helpful error message would be great.

[deepakprabhakara]

Thanks @DanHetheringtonIL, agreed we should surface the error context. We'll add that soon.