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

Question: support indexing as optional #217

Closed
ghost opened this issue Jan 13, 2019 · 3 comments
Closed

Question: support indexing as optional #217

ghost opened this issue Jan 13, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Jan 13, 2019

It would make Loki more useful for detailed searching of logs if it did indexing.

There are greats libs out there that support this in golang using badger and bleve together. They also are able to use Alisa's so that the index data is horizontally distributed as well as the act of indexing

I can suggest sone libs if required that already do the above things

The use case is of course when you need to do very detailed log searching. Facet based searching also

This is partly why elastic search is so popular with log storage - the logs are heavily indexed.

@kiney
Copy link

kiney commented Mar 6, 2019

As I understand it was a conscious design choice to not build a second elastic.

@mumoshu
Copy link

mumoshu commented Mar 25, 2019

I do second NOT to build a second elastic, but I agree on making structured logs and traces stored efficiently searchable would be useful.

For that I don't need unstructured text indexing provided by bleve, but optional indexing on structured data. #91 seems like a relevant issue.

@slim-bean
Copy link
Collaborator

Closing as a duplicate or closely related to #91

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