* refactor(searchStore): reformat filterMap function parameters (#3166) - Reformat the parameters of the filterMap function for better readability. - Comment out the fetchSessions call in clearSearch method to avoid unnecessary session fetch. * Increment frontend chart version (#3167) Co-authored-by: GitHub Action <action@github.com> * refactor(chalice): cleaned code fix(chalice): fixed session-search-pg sortKey issue fix(chalice): fixed CH-query-formatter to handle special chars fix(chalice): fixed /ids response * feat(auth): implement withCaptcha HOC for consistent reCAPTCHA (#3177) * feat(auth): implement withCaptcha HOC for consistent reCAPTCHA This commit refactors the reCAPTCHA implementation across the application by introducing a Higher Order Component (withCaptcha) that encapsulates captcha verification logic. The changes: - Create a reusable withCaptcha HOC in withRecaptcha.tsx - Refactor Login, ResetPasswordRequest, and CreatePassword components - Extract SSOLogin into a separate component - Improve error handling and user feedback - Standardize loading and verification states across forms - Make captcha implementation more maintainable and consistent * feat(auth): support msaas edition for enterprise features Add msaas to the isEnterprise check alongside ee edition to properly display enterprise features. Use userStore.isEnterprise in SSOLogin component instead of directly checking authDetails.edition for consistent enterprise status detection. * Increment frontend chart version (#3179) Co-authored-by: GitHub Action <action@github.com> * feat(assist): improved caching mechanism for cluster mode (#3180) * Increment assist chart version (#3181) Co-authored-by: GitHub Action <action@github.com> * ui: fix table column export * Increment frontend chart version * fix(auth): remove unnecessary captcha token validation (#3188) The token validation checks were redundant as the validation is already handled by the captcha wrapper component. This change simplifies the password reset flow while maintaining security. * Increment frontend chart version (#3189) Co-authored-by: GitHub Action <action@github.com> * ui: onboarding fixes * ui: fixes for onboarding ui * Increment frontend chart version * feat(helm): add TOKEN_SECRET environment variable Add TOKEN_SECRET environment variable to HTTP service deployment and generate a random value for it in vars.yaml. Signed-off-by: rjshrjndrn <rjshrjndrn@gmail.com> * fix(GraphQL): remove unused useTranslation hook (#3200) (#3206) Co-authored-by: PiRDub <pirddeveloppeur@gmail.com> * Increment frontend chart version * chore(http): remove default token_string scripts/helmcharts/openreplay/charts/http/scripts/entrypoint.sh Signed-off-by: rjshrjndrn <rjshrjndrn@gmail.com> * fix(dashboard): update filter condition in MetricsList Change the filter type comparison from checking against 'all' to checking against an empty string. This ensures proper filtering behavior when filtering metrics in the dashboard component. * Increment frontend chart version * ui: shrink icons when no space, adjust player area for events export … (#3217) * ui: shrink icons when no space, adjust player area for events export panel, fix panel size * ui: rm log * Increment frontend chart version * refactor(chalice): changed user-journey * Increment chalice chart version * refactor(auth): separate SSO support from enterprise edition Add dedicated isSSOSupported property to correctly identify when SSO authentication is available, properly handling the 'msaas' edition case separately from enterprise edition checks. This fixes SSO visibility in the login interface. * Increment frontend chart version * UI patches (28.03) (#3231) * ui: force getting url for location in tabmanagers * Assist add turn servers (#3229) * fixed conflicts * add offers * add config to sicket query * add config to sicket query * add config init * removed console logs * removed wrong updates * fixed conflicts * add offers * add config to sicket query * add config to sicket query * add config init * removed console logs * removed wrong updates * ui: fix chat draggable, fix default params --------- Co-authored-by: nick-delirium <nikita@openreplay.com> * ui: fix spritemap generation for assist sessions * ui: fix yarnlock * fix errors * updated widget link * resolved conflicts * updated widget url --------- Co-authored-by: Andrey Babushkin <55714097+reyand43@users.noreply.github.com> Co-authored-by: Андрей Бабушкин <andreybabushkin2000@gmail.com> * fix(init): remove duplicate clone Signed-off-by: rjshrjndrn <rjshrjndrn@gmail.com> * Increment assist chart version * Increment frontend chart version * ui: add old devtool filters * ui: filter keys * Increment frontend chart version * ui: fix modules mapper * ui: fix modules label * Increment frontend chart version * ui: fix double fetches for sessions * Increment frontend chart version * pulled updates (#3254) * Increment frontend chart version (#3255) Co-authored-by: GitHub Action <action@github.com> * Increment assist chart version (#3256) Co-authored-by: GitHub Action <action@github.com> * feat(chalice): added for_spot=True for authenticate_sso (#3259) * Increment chalice chart version (#3260) Co-authored-by: GitHub Action <action@github.com> * Assist patch canvas (#3265) * add agent info to assist and tracker * removed AGENTS_CONNECTED event * Increment frontend chart version (#3266) Co-authored-by: GitHub Action <action@github.com> * Increment assist chart version (#3267) Co-authored-by: GitHub Action <action@github.com> * resolved conflict * removed comments * add global method support * fix errors * remove wrong updates * remove wrong updates * add onDrag as option --------- Signed-off-by: rjshrjndrn <rjshrjndrn@gmail.com> Co-authored-by: Shekar Siri <sshekarsiri@gmail.com> Co-authored-by: Mehdi Osman <estradino@users.noreply.github.com> Co-authored-by: GitHub Action <action@github.com> Co-authored-by: Taha Yassine Kraiem <tahayk2@gmail.com> Co-authored-by: Alexander <zavorotynskiy@pm.me> Co-authored-by: nick-delirium <nikita@openreplay.com> Co-authored-by: rjshrjndrn <rjshrjndrn@gmail.com> Co-authored-by: PiRDub <pirddeveloppeur@gmail.com> |
||
|---|---|---|
| .github | ||
| api | ||
| assist | ||
| assist-server | ||
| assist-stats | ||
| backend | ||
| ee | ||
| frontend | ||
| mobs | ||
| networkProxy | ||
| scripts | ||
| snippet | ||
| sourcemap-uploader | ||
| sourcemapreader | ||
| spot | ||
| static | ||
| tracker | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| CLA.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CONTRIBUTING.md | ||
| lefthook.yml | ||
| LICENSE | ||
| README.md | ||
| README_AR.md | ||
| README_ESP.md | ||
| README_FR.md | ||
| README_RU.md | ||
| SECURITY.md | ||
| third-party.md | ||
| yarn.lock | ||
Français | Español | Русский | العربية
Session replay for developers
The most advanced session replay for building delightful web apps.
OpenReplay is an open-source session replay suite you can host yourself, that lets you see what users do on your web app, helping you troubleshoot issues faster.
- Session replay. OpenReplay replays what users do, but not only. It also shows you what went under the hood, how your website or app behaves by capturing network activity, console logs, JS errors, store actions/state, page speed metrics, cpu/memory usage and much more.
- Low footprint. With a ~26KB (.br) tracker that asynchronously sends minimal data for a very limited impact on performance.
- Self-hosted. No more security compliance checks, 3rd-parties processing user data. Everything OpenReplay captures stays in your cloud for a complete control over your data.
- Privacy controls. Fine-grained security features for sanitizing user data.
- Easy deploy. With support of major public cloud providers (AWS, GCP, Azure, DigitalOcean).
Features
- Session replay: Lets you relive your users' experience, see where they struggle and how it affects their behavior. Each session replay is automatically analyzed based on heuristics, for easy triage.
- Spot: A Chrome extension that lets record bugs directly from your browser — each recording includes all the technical details developers need to fix them.
- DevTools: It's like debugging in your own browser. OpenReplay provides you with the full context (network activity, JS errors, store actions/state and 40+ metrics) so you can instantly reproduce bugs and understand performance issues.
- Assist: Helps you support your users by seeing their live screen and instantly hopping on call (WebRTC) with them without requiring any 3rd-party screen sharing software.
- Omni-search: Search and filter by almost any user action/criteria, session attribute or technical event, so you can answer any question. No instrumentation required.
- Analytics: For surfacing the most impactful issues causing conversion and revenue loss.
- Fine-grained privacy controls: Choose what to capture, what to obscure or what to ignore so user data doesn't even reach your servers.
- Plugins oriented: Get to the root cause even faster by tracking application state (Redux, VueX, MobX, NgRx, Pinia and Zustand) and logging GraphQL queries (Apollo, Relay) and Fetch/Axios requests.
- Integrations: Sync your backend logs with your session replays and see what happened front-to-back. OpenReplay supports Sentry, Datadog, CloudWatch, Stackdriver, Elastic and more.
Deployment Options
OpenReplay can be deployed anywhere. Follow our step-by-step guides for deploying it on major public clouds:
OpenReplay Cloud
For those who want to simply use OpenReplay as a service, sign up for a free account on our cloud offering.
Community Support
Please refer to the official OpenReplay documentation. That should help you troubleshoot common issues. For additional help, you can reach out to us on one of these channels:
- Slack (Connect with our engineers and community)
- GitHub (Bug and issue reports)
- Twitter (Product updates, Great content)
- YouTube (How-to tutorials, past Community Calls)
- Website chat (Talk to us)
Contributing
We're always on the lookout for contributions to OpenReplay, and we're glad you're considering it! Not sure where to start? Look for open issues, preferably those marked as good first issues.
See our Contributing Guide for more details.
Also, feel free to join our Slack to ask questions, discuss ideas or connect with our contributors.
License
This monorepo uses several licenses. See LICENSE for more details.