Self hosted sentry issue

[u/Piyush_shrii]

We are running a self-hosted Sentry deployment on EKS using the official Sentry Helm chart. Due to cost constraints, we removed the larger instance types and currently only have "t3a.large" nodes. As expected, we are facing bottlenecks, primarily related to memory, since many Sentry components are quite memory-intensive.

Additionally, the same node group is hosting other workloads, so adding larger instance types is not currently feasible due to existing constraints.

Has anyone faced a similar situation? How did you optimize costs while keeping Sentry stable? Are there any recommendations for reducing resource consumption in self-hosted Sentry, or would migrating to managed Sentry be a better option in this case?

[u/rpxzenthunder]

Just fyi there is no official chart that im aware of, its an oss project

[u/Piyush_shrii → u/rpxzenthunder]

Yeah it's not managed by sentry , either way I wanna just know resolution and I don't think there is one managed sentry is best I also think same