-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Session Replay menu is not visible. #918
Comments
Because this is not a default option. If you would like to see this menu, you need to add:
to the |
@hiloyt |
@hiloyt I made the session replay menu appear, but does it work normally??? |
As I mentioned before, this option is set to In my company, we are using this feature and works great. Of course, you need also to edit your apps to support this feature, not only enable it for the Sentry instance. |
@hiloyt I'm not sure this is true anymore. https://github.com/getsentry/self-hosted/blob/master/sentry/sentry.conf.example.py#L253 https://github.com/sentry-kubernetes/charts/blob/develop/sentry/templates/configmap-sentry.yaml#L357 This repo doesn't seem to handle features the same way that self hosted does. This seems to overwrite the whole features array on line 357, whereas the self hosted only updates specific values. If you run a fresh install of the self-hosted version you'll have session replay and the menu using their features array, but not so with the helm version. |
@bcarroll22 They handling this exactly in the same way, but I didn't check server.py and they have this enabled from the default right now: https://github.com/getsentry/sentry/blob/master/src/sentry/conf/server.py#L1539C17-L1539C17 So they removed this flag because is not anymore needed. So something different is odd. Maybe the init process. |
Is there a reason you take the whole features array from the main Sentry repo instead of select values in the array like they do in the self-hosted repo? See here (note: link to self-hosted, not sentry): https://github.com/getsentry/self-hosted/blob/master/sentry/sentry.conf.example.py#L253 I would think the approach the chart config takes currently would make it much harder to maintain, right? |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
FYI, values.yaml config:
sentryConfPy: |
# No Python Extension Config Given
SENTRY_FEATURES["organizations:session-replay-ui"] = True |
@ohjongsung
thanks for the comment. :) |
Hello.
I upgraded to sentry 23.3.1. (18.0.0)
The relay, snuba-subscription-consumer-events, and snuba-subscription-consumer-transactions pods have errors, but the web is normally started.
However, the expected Session Replay menu is not visible.
expected Session Replay menu ㅜ
Can you tell me why?
The text was updated successfully, but these errors were encountered: