You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/data-management/event-grouping/index.mdx
+1-13Lines changed: 1 addition & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,19 +80,7 @@ Stack trace rules can work as a combination of both SDK and project settings. As
80
80
81
81
You can see a fingerprint by opening an issue, clicking "{} View JSON", and finding the _fingerprint_ property in that file. If the default grouping was used, you'll see "default" written there. If a different grouping was used, you'll see the actual fingerprint value itself.
@@ -45,7 +44,6 @@ By default, the waterfall view shows a list of transactions. If you need more gr
45
44
top: "0px",
46
45
width: "100%",
47
46
}}
48
-
title="Trace View -> Error"
49
47
></iframe>
50
48
</div>
51
49
@@ -59,68 +57,14 @@ Whatever you highlight will also be saved if you navigate away from the page and
59
57
If you're doing a comparison and want an easy way to go back and forth between highlighted areas of interest in your trace, you can pin the tabs. When a tab is pinned, the view will be persistent throughout your session.
Copy file name to clipboardExpand all lines: docs/organization/integrations/integration-platform/index.mdx
+1-13Lines changed: 1 addition & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,19 +37,7 @@ The Sentry integration platform provides the ability to add rich UI components t
37
37
You can make any integration available as an action in [issue alerts](/organization/integrations/integration-platform/webhooks/issue-alerts) and [metric alerts](/organization/integrations/integration-platform/webhooks/metric-alerts) by enabling the "Alert Rule Action" toggle. The integration will then show
38
38
up as a service in the action section when creating or updating an alert rule. The interactive demo below shows how to set up an integration that can receive Sentry alerts.
For your service to receive webhooks for alert rules, you must have `Send a notification via <your integration>` as an action in the rule. Once that's set up, you'll start receiving webhook requests for triggered alerts. For more information about the request and payload, check out the [full Webhooks documentation](/organization/integrations/integration-platform/webhooks/). If you'd like users to provide more app-specific information to handle these webhooks (e.g. assignees, teams, notification channels), consider implementing the [alert rule action UI component](/organization/integrations/integration-platform/ui-components/alert-rule-action).
You can use the dropdowns at the top of the page as a query editor for your metrics. Select the metric you want to plot from a list of available metrics in your project, the aggregate operation you'd like to perform (such as avg, min, max, and so on), and, optionally, any tags you'd like to group by. In the image above the metric `gibpotato.potatoes.event_processing_time`, is queried and shown, grouped by `event_type`.
28
16
@@ -38,19 +26,7 @@ If you'd like to zoom in and dig deeper into a particular area of your chart, dr
38
26
39
27
Sometimes observing one metric is enough to reach an insight. However, it's oftentimes necessary to look at multiple metrics simultaneously to find potential correlations.
In this case, you can create additional queries in order to compare and contrast different metrics. Click "Add Query" button to create a new query. Alternatively, you can also click "... > Duplicate" next to an existing query to create a duplicate of that query.
56
32
@@ -66,19 +42,7 @@ While metrics are a great tool for analyzing your data in aggregate and identify
66
42
67
43
Below your metric charts, the "Span Samples" tab shows a list of exemplars associated with that metric. By clicking on a span, you can navigate to the full trace view.
@@ -93,36 +57,12 @@ This feature is not currently available in all SDKs.
93
57
94
58
When it comes to custom metrics, you can use the code locations tab to see the line of code in your application where your metric is being emitted. This can come in handy when troubleshooting an issue, especially if you were not the one creating the metric in the first place.
In order to stay ahead of issues, you can also create metric-based alerts to get notified about unexpected changes or spikes. Click "... > Create Alert" next to your metric query to configure your custom metric alert.
If you want to continuously monitor a particular metric, click "... > Add to Dashboard" to create a new Dashboard widget. You can configure your dashboard to display custom metrics that matter most to you. To learn more, see [Dashboards](/product/dashboards/).
0 commit comments