Skip to content

chore(rum): send RUM to self-hosted o2 - #232

Merged
buzz-code merged 1 commit into
mainfrom
chore/rum-to-o2
Oct 22, 2026
Merged

buzz-code merged 1 commit into
mainfrom
chore/rum-to-o2

Conversation

@buzz-code

Copy link
Copy Markdown
Owner

Points the browser RUM SDK at our self-hosted OpenObserve instance instead of the cloud.

  • site: api.openobserve.ai -> o2.yoman.online
  • organizationIdentifier: hadasa_organization_50794_... -> default
  • clientToken: cloud RUM client token -> o2 RUM ingest token

The o2 token is an ingest-only credential: it authenticates POST /rum/v1/default/{rum,logs,replay} and nothing else (it is not an API/read token). Verified against o2: the same call the SDK makes returns 202 and the record lands in _rumdata / _rumlog.

Do not merge yet. This is the only app where connectToOpenobserve() is actually called, so merging switches live RUM from cloud to o2. The o2 deployment currently sends no Access-Control-Allow-Origin for https://demo.yoman.online, so the browser would ingest but the SDK would see every response as a CORS failure and retry. Merge once ZO_CORS_ALLOWED_ORIGINS on the o2 host includes this app's origin.

@buzz-code
buzz-code merged commit 3cf815b into main Oct 22, 2026
4 checks passed
@buzz-code
buzz-code deleted the chore/rum-to-o2 branch October 22, 2026 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant