hi, my team recently updated openobserve v0.14.5 to v0.80.3. and we have been facing this error with Real User Monitoring. The API calls for ingesting data are getting 200 OK. Can someone please help?

Hi @Meghna Kanade we are looking into this , and will update you shortly!

There have been several changes since v0.14.5. Since you are currently using v0.80.3, I just wanted to confirm whether you have also upgraded the Browser SDK version in your application that sends RUM data to OpenObserve. If not, could you please update the SDK version in your application's

package.json

and try again?

"@openobserve/browser-logs": "0.3.3",
"@openobserve/browser-rum": "0.3.3",

Please let me know if you are still facing issue. If required we can do quick connect on this.

@Patel Bhargav Jayantibhai sorry for the gap, _Replay segments exist and is queryable in

_sessionreplay

for session

a20cb4d9-...

, but `has_replay`/`session_has_replay` has never appeared in any

_rumdata

document org-wide — can you confirm whether this field is expected to be server-computed/enriched, or if there's a further SDK version requirement beyond 0.3.4?_

Hi @Meghna Kanade, yes, happy to set up a quick call with you to look into this. Could you share a couple of time slots that work for you, and we’ll coordinate from our side?

thanks @Simran(OpenObserve) - tomorrow 3:30pm ist works?

Apologies just now joined