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

Long term storage for Jaeger and Loki #4

Open
tumido opened this issue Feb 16, 2021 · 2 comments
Open

Long term storage for Jaeger and Loki #4

tumido opened this issue Feb 16, 2021 · 2 comments

Comments

@tumido
Copy link
Member

tumido commented Feb 16, 2021

Related to: operate-first/apps#232 for the Causter logging for DeCorus

Discussed influxDB IOx and ElasticSearch

cc @jpkrohling @RS1999ent @drbwa @eranra

@jpkrohling
Copy link

jpkrohling commented Feb 16, 2021

To give a bit more context, @RS1999ent mentioned a way to get historical data in a format that can be used at a later point in time, to which I mentioned that InfluxDB IOx will store data following the Apache Parquet format, allowing other tools to read the data. The files themselves can be stored using any block solution, like S3 for retention over longer periods of time. We also talked about Jaeger's possible plan to move to InfluxDB IOx in the future as the recommended storage mechanism, moving away from Elasticsearch. Whether that makes sense for other signals (logs, metrics), I don't know.

@drbwa
Copy link

drbwa commented Feb 18, 2021

I am aware of the trend to move to InfluxDB and maybe that is indeed the right thing to do.

From our experience, Elasticsearch allows for more convenient retrieval when it comes to log files.

What I don't know (yet) is if a) InfluxDB IOx will make it easier to slice and dice and retrieve your logs and b) how much more efficient InfluxDB is in terms of required storage space (guessing there it has an advantage there, but don't know if that's the case).

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

No branches or pull requests

3 participants