HASURA_GRAPHQL_METADATA_DATABASE_URL should allow HDB invocation logs | - Githubissues

hasura / graphql-engine

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

https://hasura.io

Apache License 2.0

31.08k stars 2.77k forks source link

HASURA_GRAPHQL_METADATA_DATABASE_URL should allow HDB invocation logs | #7580

Open sagungargs15 opened 3 years ago

sagungargs15 commented 3 years ago

Is your proposal related to a problem?

HASURA_GRAPHQL_METADATA_DATABASE_URL should allow HDB invocation logs to be separated in a new postgres DB and handle automatic migration when main DB starts getting large because of Logs

Alternate?

Manually pruning every week on self hosted solution.

PR?

Would require your help

sagungargs15 commented 3 years ago

According to the docs, I have set the metadata url and primary db url with the keys below respectively:

HASURA_GRAPHQL_METADATA_DATABASE_URL
HASURA_GRAPHQL_DATABASE_URL

Graphql engine did create few tables in the metadata_database and I can see hdb_catalog schema and few of these tables below:

hdb_catalog.hdb_action_log
hdb_catalog.hdb_cron_event_invocation_logs
hdb_catalog.hdb_cron_events
hdb_catalog.hdb_metadata
hdb_catalog.hdb_scheduled_event_invocation_logs
hdb_catalog.hdb_scheduled_events
hdb_catalog.hdb_schema_notifications
hdb_catalog.hdb_version

But after we create an event and when that event is invoked, all the invocation and event logs are still getting generated in the primary database:

hdb_catalog.event_log
hdb_catalog.event_invocation_logs

I wanted to segregate the metadata_database for mainly these two tables, which is not happening after setting metadata_database completely separate.