search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.23k stars 4.21k forks source link

Weekly reports divided by environment #50142

Open frankMmt opened 1 year ago

frankMmt commented 1 year ago

Problem Statement

Each of our projects has different environments. It would be great if there was a way to receive weekly summary reports separated by environment. This is because we are mainly interested in the issues in our production environments and not our test environments. But when the weekly report comes, we get a sum of all the errors in all environment, which is not ideal.

Is there any way to separate the weekly reports by environment, or any other way for us to generate reports only for specific environments?

Thanks!

Solution Brainstorm

No response

Product Area

Stats

getsantry[bot] commented 1 year ago

Assigning to @getsentry/support for routing, due by (sfo). ⏲️

getsantry[bot] commented 1 year ago

Routing to @getsentry/product-owners-issues for triage, due by (sfo). ⏲️

frankMmt commented 1 year ago

Hi, I have noticed that you have added this issue to your backlog. So can I assume that this would be a new feature and there is no current way to obtain weekly reports separated by environments?

Also what is your processes of prioritisation for working through backlog items? This is to say, when do you expect this to be implemented, is it a matter of weeks, months or more than that? Thanks! Francesco

patrickrbc commented 10 months ago

This would be an important feature for us. The mixing of environments in weekly reports diminishes its value.

danros commented 9 months ago

Surprised this is still not resolved. A weekly report that combines test and dev with production is basically useless.

rachrwang commented 9 months ago

@frankMmt, @patrickrbc, @danros - thanks for writing in support for this issue! We're about to revamp how the weekly report is designed and configured.

Can you share more about:

  1. How you use the weekly report today?
  2. What sections of the current weekly report you find most valuable?
  3. In addition to being able to configure by environment - are there any other filters or data cuts that you'd like to see?

cc @Dhrumil-Sentry

danros commented 9 months ago

I think the primary usecase for me would be to automatically forward the report to various stakeholders to provide them visibility of both the health our own product and the benefit of using Sentry.

Right now I can't do that as it doesn't reflect the health of our production environment.

patrickrbc commented 8 months ago

Hi!

  1. How you use the weekly report today?

There are two main things that come to my mind. The first is being aware of any incidents that happened over the past few days, and the second one is whether or not we are improving our performance.

  1. What sections of the current weekly report you find most valuable?

Error chart, Transactions/errors table, Most frequent transactions

  1. In addition to being able to configure by environment - are there any other filters or data cuts that you'd like to see?

The environment aspect is crucial, but it would also be helpful to select projects.

Trombach commented 8 months ago

@rachrwang I think it would be good if there was more control over who receives the weekly report on an organisation level. We currently have projects of multiple clients in sentry split up into multiple teams. There is no way to control who sees the weekly report emails. Ideally we would like to be able to send out weekly team based reports, but in its current form an org level switch to disable it all together would already be a great help.

rachrwang commented 8 months ago

Great, thank you everyone for your feedback! We'll follow up soon on some of upcoming updates we have in mind. Last question - how do you all feel about email as a channel vs. slack? Would it be beneficial to see this in slack as well?

Trombach commented 8 months ago

@rachrwang Slack would be great!

kdutcher commented 5 months ago

Slack as another channel would be good. For my organization, the original request of having the email separated by environment is more important.

For us, the development and qa environments are monitored by a different team than prod. We expect the lower environments to have errors - both because we have automated test cases that trigger errors and because it is new development. We do not expect production to have errors. The prod support team monitors the individual error emails, but the managers look at the weekly.

PeterKneale commented 4 months ago

Any update on this, I'm experiencing the same issue where the value of the weekly reports is nil because it contains all of the noise from dev and test environments.

roggenkemper commented 4 months ago

@PeterKneale sorry, there's no timeline right now on adding this feature