PID failure logs only seems to work with api calls

[nightowlaz]

We recently enabled the enable-pid-failure-log feature flag (Feature flag:
-Ddataverse.feature.enable-pid-failure-log=true) in our QA and Prod sites .. and I see logs being created.

I did a bunch of testing to see what it is logging with various methods of requesting an invalid DOI. The documentation and PR for enable-pid-failure-log suggest that failed dataset/file PID lookups should be logged. In Dataverse 6.10.1, failed lookups via /api/datasets/:persistentId are logged, but failed lookups via /dataset.xhtml?persistentId=... are not. Is this the intended behavior, or should the JSF landing page also generate PID failure log entries?

What steps does it take to reproduce the issue?
curl -i "https:///api/datasets/:persistentId/?persistentId=doi:10.5072/FK2/" (logs)
curl -i "https:///dataset.xhtml?persistentId=doi:10.5072/FK2/" (does not log)
OR:
from browser:
https:///api/datasets/:persistentId/?persistentId=doi:10.5072/FK2/ (logs)
https:///dataset.xhtml?persistentId=doi:10.5072/FK2/ (does not log)

• When does this issue occur?
  when a bad PID is entered using the dataset landing page URL

• What happens?
  does not create log in PIDFailures_.log

Which version of Dataverse are you using?
v6.10.1

[qqmyers]

FWIW: I suspect this was broken at some point as we tried to increase efficiency - the logging is in DatasetServiceBean.findByGlobalId (which retrieves the whole dataset) but the dataset page now uses the findIdByGlobalId method (which just returns the id value itself), bypassing the logging (but more efficient).