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: develop-docs/development/environment/index.mdx
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -288,3 +288,9 @@ docker ps
288
288
**Problem:** You use an Android emulator with a DSN pointing to localhost, and the events don't show up in your local Sentry instance.
289
289
290
290
**Solution:** Change `localhost` to `10.0.2.2`. So, for example, change http://d895df97e1cb4a33b4dff8af3e78da09@localhost:8000/2 to http://[email protected]:8000/2. This is because localhost or `127.0.0.1` refers to the emulator's own loopback interface, not the loopback interface of the host machine. For more information see https://developer.android.com/studio/run/emulator-networking.
291
+
292
+
---
293
+
294
+
**Problem:** Switching from Docker Desktop to Colima results in error `Failed to start service: Credentials store error: StoreError('docker-credential-desktop not installed or not available in PATH')`
295
+
296
+
**Solution:** Remove the `credsStore` key in your `~/.docker/config.json` file.
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).
0 commit comments