Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate possibility of logging to PostgreSQL #5

Open
spbnick opened this issue Feb 14, 2017 · 1 comment
Open

Investigate possibility of logging to PostgreSQL #5

spbnick opened this issue Feb 14, 2017 · 1 comment

Comments

@spbnick
Copy link
Member

spbnick commented Feb 14, 2017

PostgreSQL has recently added support for JSON storage and indexing.
@plaes asked if something like this could be used for the backend.

Investigate what's possible with this solution and what it could take, roughly, to use it.

See https://fosdem.org/2017/schedule/event/postgresql_infrastructure_monitoring/
and http://www.slideshare.net/StevenSimpson30/infrastructure-monitoring-with-postgres

@spbnick spbnick modified the milestone: Bright future Feb 15, 2017
@spbnick
Copy link
Member Author

spbnick commented Mar 5, 2017

If anybody is going to be using a system like this, then it is likely that there will be a place for ingesting tlog/aushape JSON as is in the stack, and no additional code will need to be done on our part. The data will be stored as JSONB and would allow sorting and queries for data sufficient for playback purposes, with retrieval of original JSON, I assume. Technically there doesn't seem to be any major hurdles to implementing this. However, separate retrieval and querying back-ends will have to be used compared to Elasticsearch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant