I'm evaluating Greptimedb in prod and while I hate to have a needless component like OTEL-Collector in general, it serves as a read-only gate between the database and the user, so that greptime keeps listening to localhost only, and OTEL-Collector guarantees nobody will write to the database directly.

If it were to give more fine-grained control over write-only access -- would probably just write directly and let it handle the load.

▲

killme2008 4 days ago | parent [-]

Thank you for evaluating GreptimeDB.

We agree that fine-grained access control is important. A read-only user role will be available in the next major release.

	▲	kjuulh 4 days ago \| parent \| next [-]
		I had a brief look at greptime db. And I'd like to give a little bit of feedback on your funnel. It is clear that your product marketing is targeting business folks rather than developers. That 3 minute vid on the frontpage was next to useless for me. Also very clearly AI. Having stats is nice but i am not choosing your product because of stats. I actually think greptimedb is exactly what I am looking for, I.e. a humio / falcon logscale alternative. But I had to do some digging to actually infer that. Your material doesn't highlight what sets you apart from the competition. If you want to target developers which you might not. I dont know. I want to debug issues using freetext search, i want to be able to aggregate stats i care about on demand.
	▲	k_bx 4 days ago \| parent \| prev [-]
		I understand that it's mostly for enterprise users, but please also add ability to limit which databases can a user see and add a "write-only" access. Or maybe I'll contribute this piece myself when I'll have time :) p.s.: btw, I love Greptime so far, thank you for the product!