IBX-11507: Critical errors logged when browsing BackOffice as user with limited permissions

[Sztig]

🎫 Issue	IBX-11507

Description:

This is a "hotfix" for excessive error logging when using backoffice as a user with limited permissions. The fix is not perfect as it silences the logging entirely.

Alternatives considered:
Make ArgumentsException extend UserWarning and remove the previous exception

• silences logging entirely
• loses stack trace
• possible BC break?

Catch ArgumentsException in resolvers and re-throw as UserError/return null

• would need to patch every resolver that calls findSingle
• changes what callers receive ergo BC break?

The underlying issue is that we are no matter what querying all the info about content so depending on the permissions, other users will throw different errors in the logs while the backoffice functions as intended.
Fixing this by checking permissions seems to be too expensive/complex of a fix.

[ViniTou]

This is no way to go, we cant just disable all logging.

Is it possible to use Monolog\Handler\AbstractProcessingHandler for it, and maybe check for namespace/class (Ibexa\GraphQL\DataLoader\Exception\ArgumentsException) or stacktrace in given exception, and when it match graphql we then ignore it?

or even better maybe we can easly configure it to log those into specific channel?

[Sztig]

I've done some test and something like this seem to work - how about we log it under the default app.DEBUG or new channel like graphql.DEBUG instead of app.CRITICAL so it is still being logged but not in the production?

[konradoboza]

@Sztig if what you meant is logging GraphQL issues in a separate channel then I think we should indeed go for it.

[konradoboza]

Also, CI on PHP 7.4 is fixed, feel free to rebase this PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Sztig]

So I have went with this approach - I have added new channel called graphql and through a listener send all the ArgumentsException exceptions there.
While it doesn't stop logging these exceptions, muting them specifically is now very easy.