Graphql-engine: Verbose logging

Created on 21 Sep 2018 · 5Comments · Source: hasura/graphql-engine

via @praveenweb:

"we should enable verbose logging mode (via flag/env), where instead of just the query_hash, we get the actual query for better debugging".

server enhancement medium

Source

dsandip

👍3

Most helpful comment

I would like to point out that verbose logging is important for subscriptions as well. At the moment performance values are logged only for queries.

martinzwirner on 13 Feb 2019

👍2

All 5 comments

I would also like to see this feature for audit purposes. Logging queries and response times will enable analysis and reporting to aid detection of attacks and broken clients.

In the event of a security breach, query logging will be needed to see which data the attacker accessed.

elgordino on 18 Dec 2018

👍2

from Prashantha on Discord - additional info needed: the PG tables/columns being accessed

dsandip on 5 Feb 2019

👍1

Let's also add some numbers from #428 (which I am closing in favor of this one)

dsandip on 13 Feb 2019

I would like to point out that verbose logging is important for subscriptions as well. At the moment performance values are logged only for queries.

martinzwirner on 13 Feb 2019

👍2

Any chance verbose logging could also spit out whether Hasura thinks you've configured it to use JWTs? Just had an issue where the HASURA_GRAPHQL_JWT_SECRET wasn't being set the right way because Windows.