grafana / explore-logs

Repo for the Loki log exploration app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

check scale and gracefully degrade

matryer opened this issue · comments

For the top 40 users, we are not going to provide Explore Logs.

We could check the scale in the frontend and show a nice message with Grot saying something like, "Sorry, we're not ready for your scale yet. We're working hard to enable Explore Logs for your org. Meanwhile, get in touch if you'd like to run some experiments."

Owen: You want loki_tenant_bytes_rate5m

@cyriltovena /loki folks. How would the frontend determine scale? What's the desired limit?
@ivanahuckova or @svennergr: We're currently deploying to a hardcoded list of instances, for public preview can we deploy to all except an exclude list?

@gtk-grafana rather than have something missing (if they hear about it and can't find the link, they might think something is broken.) I wonder if we should install it for them but show an info message. If someone at one of the big companies is interested in doing some testing at scale, it could be a nice way to find those people. But not deploying it also works if it's significantly easier/simpler.

@matryer That query could help us create a list of users not to deploy to, but we're not going to be able to execute queries against ops-cortex in the user's instance. I guess it might be possible to create a feature flag for users we've "disabled", and add some custom functionality if that flag is active.

@gtk-grafana got it - thanks. Is there a way to add some config for those people and check that?

@cyriltovena is there another way we can do this? Not checking ops, but checking THEIR data?