Zalando Logbook separate configuration from client and server side

[honza-zidek]

Is it possible to configure Zalando Logbook separately for the server side logging (incoming requests) and the client side logging (outgoing requests)?

I'd like to log only some incoming requests (/api/** and /int/**), but all the outgoing requests not regarding their URI (/**).

Following the documentation https://gitee.com/kedocode/logbook#configuration, something like:

logbook:
  server:
    predicate:
      include:
        - path: /api/**
        - path: /int/**
  client:
    predicate:
      include:
        - path: /**

The above configuration was the solution suggested by ChatGPT, but it doesn't seem to work, however the idea was good.

[kasmarian]

It's not possible with the Spring Boot configuration in the current state, unfortunately. You can define your own Predicate<HttpRequest> beans that will have this logic, though.

[whiskeysierra]

Just to add to that: A custom predicate has full access to the HTTP request, including what we call the origin which is either LOCAL (for requests that means you are the client) and REMOTE (you are the server).

If you don't want to implement path expressions yourself (Trust me - you don't!) the I'd suggest you use requestTo in Conditions to construct yourself two predicates, one for client and one for the server case, store them as fields (you only need to construct those once) and after you checked the origin, you delegate to either of those.

Based on your example above, the server uses two paths. For that you might need to predicates that you compose with and.

[github-actions]

In order to prioritize the support for Logbook, we would like to check whether the old issues are still relevant.
This issue has not been updated for over six months.

• Please check if it is still relevant in latest version of the Logbook.
• If so, please add a descriptive comment to keep the issue open.
• Otherwise, the issue will automatically be closed after a week.

[honza-zidek]

Of course it is still relevant :)
The suggested workaround is possible, but awkward and unnecessarily complicated.
The solution suggested in the issue description is clean and follows the logic of Zalando.