mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-16 18:42:30 +03:00
a21f6cd648
Changes compared to `/v1alpha1/graphql` * Changed all graphql responses in **/v1/graphql** endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. * Errors in http and websocket layer are now consistent and have similar structure.
21 lines
858 B
ReStructuredText
21 lines
858 B
ReStructuredText
Hasura GraphQL engine server logs (Kubernetes)
|
|
==============================================
|
|
|
|
.. contents:: Table of contents
|
|
:backlinks: none
|
|
:depth: 1
|
|
:local:
|
|
|
|
You can check logs of Hasura GraphQL engine deployed on Kubernetes by checking the logs of the GraphQL engine
|
|
service, i.e. ``hasura``:
|
|
|
|
.. code-block:: bash
|
|
|
|
$ kubectl logs -f svc/hasura
|
|
|
|
{"timestamp":"2018-10-09T11:20:32.054+0000", "level":"info", "type":"http-log", "detail":{"status":200, "query_hash":"01640c6dd131826cff44308111ed40d7fbd1cbed", "http_version":"HTTP/1.1", "query_execution_time":3.0177627e-2, "request_id":null, "url":"/v1/graphql", "user":{"x-hasura-role":"admin"}, "ip":"127.0.0.1", "response_size":209329, "method":"POST", "detail":null}}
|
|
...
|
|
|
|
|
|
See https://kubernetes.io/docs/concepts/cluster-administration/logging for more details on logging in Kubernetes.
|