sentry icon indicating copy to clipboard operation
sentry copied to clipboard

Filter alerts by dynamic tag value

Open OmerCohenAviv opened this issue 9 months ago • 3 comments

Problem Statement

Problem: Need to be able to create an alert that will be triggered by a tag value that is dynamic.

Why? Our company is b2c and every client has his configurations etc to the application... We need to be able to react to any errors / slowness per client. The company has a large list of clients and is expanding fast.

P.S - we need to duplicate those alerts across teams as we use micro-frontends, if you know about any solution for it

Solution Brainstorm

Add the option to add a dynamic value to filters

Product Area

Alerts

OmerCohenAviv avatar May 21 '24 12:05 OmerCohenAviv

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] avatar May 21 '24 12:05 getsantry[bot]

Routing to @getsentry/product-owners-alerts for triage ⏲️

getsantry[bot] avatar May 22 '24 11:05 getsantry[bot]

@OmerCohenAviv - thanks for sharing this feature idea.

I wanted to clarify the example you provided above:

  • In your example, does the "dynamic tag value" refer to a client identifier, or something else?
  • If you were able to split your alerts by this tag, would you still want the same thresholds for each tag value, or a differing threshold per tag value?
  • What is the relationship between your teams and projects today? Can you share more about your setup - i.e. do you have different teams sharing the same Sentry project, do they each map to their own project, or is there a different configuration altogether?

rachrwang avatar May 22 '24 16:05 rachrwang

Hi @rachrwang thanks for replying on this,

  1. Yes exactly, Dynamic tag value refers to the client client identifier,
  2. This is a good point, as each client is on different scale, it make sense to have different thresholds, but as first step it's not a requirement.
  3. We are using module-federation to render pages that belong to teams, each team can own serval pages. on our frontend we send errors and transactions to relevant projects.
  • About thresholds for each tag, this is a bit harder, as we don't want to configure each threshold explicitly as we have hundreds of clients and we are expanding quick. it will make more sense if it's possible that thresholds will be inherited by tag or other configuration for example client_size='large' could have thresholds of x, where client_size=enterprise will have thresholds of y etc...

  • We tried to configure our alerts on client using terraform but quickly met with limitation on the number of metric alerts.

Thanks again :)

OmerCohenAviv avatar May 22 '24 16:05 OmerCohenAviv

That's super helpful context, thank you @OmerCohenAviv! This is an area that we're discussing expanding alerts on, though we aren't actively building this right now. I've logged your feature request and will let you know when we have any updates.

rachrwang avatar May 22 '24 19:05 rachrwang