You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Version:
CLI Version (for CLI related issue):
Environment
On EKS, I'm using helm hasura to deploy.
What is the current behaviour?
When I check logs of pod in hasura-graphql-engine. I receiver many wrong messages and I don't know how to fix it. {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"192.168.33.52","method":"GET","status":200,"url":"/healthz"},"operation":{"query":{"type":null},"request_id":"daa819d3-338c-4db9-8318-8dc58a43f3d9","request_mode":"non-graphql","response_size":36,"uncompressed_response_size":36},"request_id":"daa819d3-338c-4db9-8318-8dc58a43f3d9"},"level":"info","timestamp":"2025-01-12T05:01:26.832+0000","type":"http-log"} {"detail":{"info":"Received metadata resource version: 314, different from the current engine resource version: 29. Trying to update the schema cache.","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":"Fetched metadata with resource version: 314","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":"Fetched metadata notifications and received some notifications. Updating the schema cache.","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":{"message":"source \"ar2\" is already at the latest catalog version (3).","source":"ar2"},"kind":"source_catalog_migrate"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"startup"} {"detail":{"info":"Schema cache updated with resource version: 314","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"192.168.86.180","method":"GET","status":200,"url":"/healthz"},"operation":{"query":{"type":null},"request_id":"5bd8bf5c-e798-42a0-a5a3-da7e1545aa3f","request_mode":"non-graphql","response_size":36,"uncompressed_response_size":36},"request_id":"5bd8bf5c-e798-42a0-a5a3-da7e1545aa3f"},"level":"info","timestamp":"2025-01-12T05:01:28.364+0000","type":"http-log"}
What is the expected behaviour?
Don't appear any wrong messages
Screenshots or Screencast
The text was updated successfully, but these errors were encountered:
Version Information
Server Version:
CLI Version (for CLI related issue):
Environment
On EKS, I'm using helm hasura to deploy.
What is the current behaviour?
When I check logs of pod in hasura-graphql-engine. I receiver many wrong messages and I don't know how to fix it.
{"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"192.168.33.52","method":"GET","status":200,"url":"/healthz"},"operation":{"query":{"type":null},"request_id":"daa819d3-338c-4db9-8318-8dc58a43f3d9","request_mode":"non-graphql","response_size":36,"uncompressed_response_size":36},"request_id":"daa819d3-338c-4db9-8318-8dc58a43f3d9"},"level":"info","timestamp":"2025-01-12T05:01:26.832+0000","type":"http-log"} {"detail":{"info":"Received metadata resource version: 314, different from the current engine resource version: 29. Trying to update the schema cache.","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":"Fetched metadata with resource version: 314","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":"Fetched metadata notifications and received some notifications. Updating the schema cache.","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"info":{"message":"source \"ar2\" is already at the latest catalog version (3).","source":"ar2"},"kind":"source_catalog_migrate"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"startup"} {"detail":{"info":"Schema cache updated with resource version: 314","thread_type":"processor"},"level":"info","timestamp":"2025-01-12T05:01:27.833+0000","type":"schema-sync"} {"detail":{"http_info":{"content_encoding":null,"http_version":"HTTP/1.1","ip":"192.168.86.180","method":"GET","status":200,"url":"/healthz"},"operation":{"query":{"type":null},"request_id":"5bd8bf5c-e798-42a0-a5a3-da7e1545aa3f","request_mode":"non-graphql","response_size":36,"uncompressed_response_size":36},"request_id":"5bd8bf5c-e798-42a0-a5a3-da7e1545aa3f"},"level":"info","timestamp":"2025-01-12T05:01:28.364+0000","type":"http-log"}
What is the expected behaviour?
Don't appear any wrong messages
Screenshots or Screencast
The text was updated successfully, but these errors were encountered: