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

Logs volume should not use parser if not needed #143

Closed
ivanahuckova opened this issue Apr 3, 2024 · 3 comments
Closed

Logs volume should not use parser if not needed #143

ivanahuckova opened this issue Apr 3, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@ivanahuckova
Copy link
Member

ivanahuckova commented Apr 3, 2024

@cyriltovena the largest query on service index page - to fetch to top services is not using any parser
image

However, on the service detail page, it would be more complex to determine whether we have some detected fields selected or not (if we need a parser to make query with detected fields work). Of course, it is doable, but considering at the moment, have a lot of issues with state, I would probably wait to resolve them and then optimize when this is more stable.

So keeping this in No Status

Also more in https://raintank-corp.slack.com/archives/C05FWM2DN07/p1712171252433889?thread_ts=1712165843.027599&cid=C05FWM2DN07

@gtk-grafana gtk-grafana added the bug Something isn't working label Apr 5, 2024
@ivanahuckova
Copy link
Member Author

Blocked by detected_fields PR and refactor of query creation logic.

@ivanahuckova
Copy link
Member Author

Might be solved by #257

@gtk-grafana
Copy link
Contributor

Should be fixed by #736

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants