I don't think that there is a particular way to do this in graphene-django community.. but your method is very good unless the code need to be cleared and well structured for reuse and customize using configurations.

BUT

I wouldn't choose to ignore the well strucutred error message which can django forms give when using with graphene mutations, also, your method is generalized for all the queries and mutations.. that you can do in your app, so it need to be maintained carefully.

But it is inspiring method to have customized logging for graphql requests for example.