<!channel> 🚀 This week in OpenObserve Big shoutout to @Gaby and @Simon Novak for showing up in the community, answering questions and helping people get unblocked. Here's what shipped: ✨ What's New • Vortex search engine moved from Enterprise into open source, everyone gets the faster indexing now, not just enterprise customers. • MCP server is fully OSS now, plus OAuth 2.0 sign-in for MCP, which also closed a cross-org RBAC bypass and an expired-JWT bug. Worth checking if you run MCP in prod. • Self-correcting search, typo a field or function name and you'll get a "did you mean" suggestion instead of an empty result. • Dashboards got a redesigned panel config and a reworked gallery drawer with migration links built in. • Traces now default to Waterfall view. • Org-level AI credit management for Cloud, track and cap AI usage per org instead of one shared pool. • New

_search

agent options, mode=partition and output_format=csv/md_table, useful if you're building on top of the API. 🛠️ What's Fixed • Sensitive-data redaction now applies to traces too, not just logs. • Agent Graph correctness fixes. • Logs sidebar table is the default view now with draggable tabs, and share-link query restoration bugs are fixed. • Memtable rotation fixed and schema persistence guard restored, both reliability fixes under the hood. 139 PRs merged this week, nearly double last week's pace. Which of these are you most excited to try, and what's still bugging you that didn't make the list? 👇

The docs still state that MCP is an enterprise feature. In the OSS there are no RBAC or Read-Only accounts which makes using MCP very dangerous as they could randomly decide to delete a stream/account/etc.

Good catch on the docs, we'll get that updated. As for RBAC, it's an Enterprise-only feature. If you need read-only roles or fine-grained permissions for MCP, you'll need to use the Enterprise edition.

@Simran(OpenObserve) There's no point in enabling MCP without access control. LLM are non-deterministic and can randomly decide to call a tool that deletes all of O2

Yes, RBAC is a guardrail but only after the MCP layer. To be fair, the responsibility of stopping dangerous actions fall upon the client side harness rather than the server. Id suggest looking into tool confirmation layer ( check o2 ai ) and allowlist for mcp tools for your agents. Most harnesses already support both. Happy to implement more guardrails in oss mcp if you have other ideas.

@Uddhav Maybe add an ENV to only allow Read-Only actions via the MCP ?

we can explore that direction. can you raise an issue please?