chore(sentryapp): new `SentryAppWebhookRequestsEndpoint` control endpoint #81676

ameliahsu · 2024-12-04T18:14:16Z

We need a new control endpoint in order to fetch sentry app requests from all regions.

Note:
Since installation requests are stored in control, we also have to fetch requests from the control buffer. We specifically query the region buffers for non-installation event requests to avoid duplicate requests (in case a region shares the same buffer as control).

codecov · 2024-12-04T18:38:03Z

Codecov Report

Attention: Patch coverage is 99.40120% with 1 line in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...c/sentry/sentry_apps/api/utils/webhook_requests.py	98.03%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #81676      +/-   ##
==========================================
+ Coverage   80.41%   81.24%   +0.82%     
==========================================
  Files        7241     7280      +39     
  Lines      321573   338135   +16562     
  Branches    20830    20830              
==========================================
+ Hits       258604   274723   +16119     
- Misses      62574    63017     +443     
  Partials      395      395

cathteng

i think there is some opportunity to condense code here

cathteng · 2024-12-04T22:50:51Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+    publish_status = {
+        "GET": ApiPublishStatus.UNKNOWN,
+    }
+    permission_classes = (SentryAppStatsPermission,)


should this be SentryAppPermission?

SentryAppStatsPermission is the one to use for this endpoint, since we only want the integrator org to be able to get the requests/stats.

there seems to only be a GET for this endpoint, so only the GET scopes would apply. the PARANOID_GET scopes from SentryAppPermission applies to anyone with member and above permissions which also seems appropriate

cathteng · 2024-12-04T22:51:20Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        event_type = request.GET.get("eventType")
+        errors_only = request.GET.get("errorsOnly")
+        org_slug = request.GET.get("organizationSlug")
+        start_parameter = request.GET.get("start", None)
+        end_parameter = request.GET.get("end", None)


you can use a serializer class to validate these rather than have it done inside the endpoint, like this

sentry/src/sentry/api/endpoints/api_tokens.py

Lines 81 to 84 in 329a08d

serializer = ApiTokenSerializer(data=request.data)

if serializer.is_valid():

result = serializer.validated_data

this is for this entire section before the "major changes" part

cathteng · 2024-12-04T22:57:43Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        if event_type == "installation.created" or event_type == "installation.deleted":
+
+            requests.extend(
+                [
+                    serialize_rpc_sentry_app_request(req)
+                    for req in buffer.get_requests(
+                        event=event_type, errors_only=control_errors_only
+                    )
+                ]
+            )
+        elif event_type is None:
+            control_event_type = [
+                "installation.created",
+                "installation.deleted",
+            ]
+            requests.extend(
+                [
+                    serialize_rpc_sentry_app_request(req)
+                    for req in buffer.get_requests(
+                        event=control_event_type, errors_only=control_errors_only
+                    )
+                ]
+            )
+
+        # If event type is installation.created or installation.deleted, we don't need to fetch requests from other regions
+        if event_type != "installation.created" and event_type != "installation.deleted":
+            for region_name in find_all_region_names():
+                buffer_requests = app_request_service.get_buffer_requests_for_region(
+                    sentry_app_id=sentry_app.id,
+                    region_name=region_name,
+                    filter=filter,
+                )
+                if buffer_requests is not None:
+                    requests.extend(buffer_requests)


is there a better way to write this? i think there's a lot of repeated code where you extend the list of requests. the first two ifs are REALLY similar other than changing the event

cathteng · 2024-12-04T22:58:40Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+class SentryAppRequestsEndpointV2(SentryAppBaseEndpoint):
+    owner = ApiOwner.INTEGRATIONS
+    publish_status = {
+        "GET": ApiPublishStatus.UNKNOWN,


if we plan to publish this in the future, this can be ApiPublishStatus.EXPERIMENTAL

cathteng · 2024-12-04T22:59:49Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        for i, req in enumerate(requests):
+            if filter_by_date(req, start_time, end_time) and filter_by_organization(
+                req, organization
+            ):
+                filtered_requests.append(BufferedRequest(id=i, data=req))


is it possible to filter the requests before we even add them to the list, so we don't have to iterate over them again? this is where i think a helper function would be useful, for this part and the repeated logic above

GabeVillalobos · 2024-12-05T23:41:04Z

src/sentry/api/urls.py

@@ -2906,6 +2907,11 @@ def create_group_urls(name_prefix: str) -> list[URLPattern | URLResolver]:
        SentryAppPublishRequestEndpoint.as_view(),
        name="sentry-api-0-sentry-app-publish-request",
    ),
+    re_path(
+        r"^(?P<sentry_app_id_or_slug>[^\/]+)/requests-v2/$",


Instead of encoding requests-v2 in the path, could we instead name this something different? Like request-logs or webhook-responses?

GabeVillalobos · 2024-12-05T23:41:42Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        choices=EXTENDED_VALID_EVENTS,
+        required=False,
+    )
+    errors_only = serializers.BooleanField(required=False)


Setting a default value here would be nice.

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

GabeVillalobos · 2024-12-05T23:47:55Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        if "start" in data and "end" in data and data["start"] > data["end"]:
+            raise serializers.ValidationError("Invalid timestamp (start must be before end).")


Could we combine this with the validation for validate_end? This seems like a field error on end vs a general exception.

We have to use validate in order to access multiple fields (in this case start and end) 😔

GabeVillalobos · 2024-12-05T23:50:53Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        def filter_and_append_requests(unfiltered_requests: list[RpcSentryAppRequest]) -> None:
+            for i, req in enumerate(unfiltered_requests):
+                if filter_by_date(req, start_time, end_time) and filter_by_organization(
+                    req, organization
+                ):
+                    requests.append(BufferedRequest(id=i, data=req))
+
+        def get_buffer_requests_for_control(event_type) -> list[RpcSentryAppRequest]:
+            control_requests = [
+                serialize_rpc_sentry_app_request(req)
+                for req in control_buffer.get_requests(
+                    event=event_type, errors_only=control_errors_only
+                )
+            ]
+            filter_and_append_requests(control_requests)
+
+        def get_buffer_requests_for_regions() -> list[RpcSentryAppRequest]:
+            for region_name in find_all_region_names():
+                buffer_requests = app_request_service.get_buffer_requests_for_region(
+                    sentry_app_id=sentry_app.id,
+                    region_name=region_name,
+                    filter=region_filter,
+                )
+                if buffer_requests is not None:
+                    filter_and_append_requests(buffer_requests)


Instead of nesting these closures, could these live in a separate class/service that handles retrieving buffer requests? I could see a case where we use these outside of this endpoint.

GabeVillalobos · 2024-12-05T23:52:18Z

src/sentry/sentry_apps/api/endpoints/sentry_app_requests_v2.py

+        def data_fn(offset, limit):
+            page_offset = offset * limit
+            return requests[page_offset : page_offset + limit]
+
+        return self.paginate(
+            request=request,
+            paginator=GenericOffsetPaginator(data_fn),
+            on_results=lambda x: serialize(x, request.user, RequestSerializer(sentry_app)),
+        )


Will this paginate correctly? I'm concerned the results will be weird if an org has a high volume of webhooks and older request buffer responses are constantly rotating off.

Also, do we need to be paginating if our limit is ~100 buffers per region?

Just updating here that we decided to remove pagination

GabeVillalobos · 2024-12-05T23:53:18Z

src/sentry/sentry_apps/api/serializers/request_v2.py

+from sentry.sentry_apps.models.sentry_app import SentryApp
+
+
+class RequestSerializer(Serializer):


This name is a bit generic, could we make it more specific to SentryApp Webhook Requests?

GabeVillalobos · 2024-12-05T23:56:29Z

src/sentry/sentry_apps/api/serializers/request_v2.py

+        self.sentry_app = sentry_app
+
+    def get_attrs(
+        self, item_list: Sequence[Any], user: Any, **kwargs: Any


Is is possible to add more narrow typing to item_list and user?

src/sentry/sentry_apps/services/app_request/model.py

github-actions · 2024-12-06T22:21:29Z

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

codecov · 2024-12-06T22:25:42Z

Bundle Report

Changes will increase total bundle size by 136.86kB (0.43%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
app-webpack-bundle-array-push	32.11MB	136.86kB (0.43%) ⬆️

iamrajjoshi

looks good, good job!

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py

Christinarlong

UHHH I FORGOT TO CLICK SUBMIT. I did this on monday so it may be out of date

Christinarlong · 2024-12-16T17:39:31Z

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py

+    def validate_end(self, end):
+        if end is None:
+            end = datetime.now(tz=timezone.utc)
+        return end


Q: where does this get used ?

This is called when .is_valid() is called (same as validate above). See docs here

Christinarlong · 2024-12-16T17:59:06Z

src/sentry/sentry_apps/api/serializers/sentry_app_webhook_request.py

+                    organizations_by_id.get(item.data.organization_id)
+                    if item.data.organization_id
+                    else None
+                )


if we know the shape of the data we could TypedDict this instead of Mapping[Any,Any]

Christinarlong · 2024-12-16T18:00:02Z

src/sentry/sentry_apps/api/serializers/sentry_app_webhook_request.py

+
+    def serialize(
+        self, obj: Any, attrs: Mapping[Any, Any], user: Any, **kwargs: Any
+    ) -> Mapping[str, Any]:


Same as above 🥺

Agreed. Avoid using Any typing unless absolutely necessary.

Christinarlong · 2024-12-16T18:07:08Z

src/sentry/utils/sentry_apps/request_buffer.py

-    def _get_requests(self, event: str | None = None, error: bool = False) -> list[dict[str, Any]]:
+    def _get_requests(
+        self, event: str | list[str] | None = None, error: bool = False
+    ) -> list[dict[str, Any]]:


is the list composed of RpcSentryAppRequest or SentryAppRequests?

We have to translate the results of this function call into an RpcSentryAppRequest, so I don't think we can type this?

sentry/src/sentry/sentry_apps/api/utils/webhook_requests.py

Lines 71 to 72 in e1aa641

serialize_rpc_sentry_app_request(req)

for req in control_buffer.get_requests(event=event, errors_only=errors_only)

I think we can ? It looks like we know what's going to be in the request data for that serializer so we could type the return here.

Christinarlong · 2024-12-16T18:12:41Z

tests/sentry/sentry_apps/api/endpoints/test_sentry_app_webhook_requests.py

+
+        response2 = self.client.get(f"{url}?eventType=issue.assigned", format="json")
+        assert response2.status_code == 200
+        assert len(response2.data) == 1


it would be good to test the shape of the data is what we want

Christinarlong · 2024-12-16T18:59:57Z

tests/sentry/sentry_apps/api/endpoints/test_sentry_app_webhook_requests.py

We should add some tests to for cross region functionality
e.g two different orgs in diff regions do something that adds to buffer

validate that the requests are not in the same buffer

validate that when we get the requests both reqs show up

etc. ( I can add more cases in a bit)

I talked to Gabe about this and we said we wouldn't test cross region, since it's not easy to mock multiple Redis instances

Yeah, unfortunately I don't think we have the testing infrastructure for this unless the redis key we're generating in each silo is distinct somehow. Worth verifying at least, but I'm not sure it's worth the extra effort when we can manually validate this behavior ourselves using feature flags.

sentaur-athena

I started reviewing but then I realized there are multiple open questions that I also have too. Can you address them and ping the channel again?

sentaur-athena · 2024-12-19T00:31:10Z

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py

+
+@control_silo_endpoint
+class SentryAppWebhookRequestsEndpoint(SentryAppBaseEndpoint):
+    owner = ApiOwner.INTEGRATIONS


You can update this to ecosystem. Integrations is the old stuff.

GabeVillalobos · 2024-12-07T00:40:09Z

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py

+
+        def filter_and_append_requests(unfiltered_requests: list[RpcSentryAppRequest]) -> None:
+            for i, req in enumerate(unfiltered_requests):
+                if self._filter_by_date(req, start_time, end_time) and self._filter_by_organization(


This logic living here is a bit unusual. Could we move this date filtering behavior into the get_buffer_requests_from_control and get_buffer_requests_from_regions helper functions instead? I could also see this being a standalone utility method for general RpcSentryAppRequest filtering.

Pulling more of this business logic out of the controller and putting it into shared modules will help with reusability and testing.

GabeVillalobos · 2024-12-19T18:01:38Z

src/sentry/sentry_apps/api/serializers/sentry_app_webhook_request.py

+
+    def serialize(
+        self, obj: Any, attrs: Mapping[Any, Any], user: Any, **kwargs: Any
+    ) -> Mapping[str, Any]:


Agreed. Avoid using Any typing unless absolutely necessary.

GabeVillalobos · 2024-12-19T18:03:29Z

tests/sentry/sentry_apps/api/endpoints/test_sentry_app_webhook_requests.py

Yeah, unfortunately I don't think we have the testing infrastructure for this unless the redis key we're generating in each silo is distinct somehow. Worth verifying at least, but I'm not sure it's worth the extra effort when we can manually validate this behavior ourselves using feature flags.

GabeVillalobos · 2024-12-19T18:04:29Z

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py

+        :qparam string start: Optionally specify a date to begin at. Format must be YYYY-MM-DD HH:MM:SS
+        :qparam string end: Optionally specify a date to end at. Format must be YYYY-MM-DD HH:MM:SS
+        """
+        serializer = IncomingRequestSerializer(data=request.GET)


Do we want to gate access here with a feature flag maybe? We may want to validate the behavior of this endpoint before releasing it to the public.

Would marking the endpoint as experimental be enough? I think we could update the callee side to use this new endpoint to test then roll the cutover out to few customers before going public.

Update: We decided to feature flag this endpoint while we test fetching requests from multiple regions

Christinarlong · 2024-12-19T21:14:14Z

src/sentry/utils/sentry_apps/request_buffer.py

-    def _get_requests(self, event: str | None = None, error: bool = False) -> list[dict[str, Any]]:
+    def _get_requests(
+        self, event: str | list[str] | None = None, error: bool = False
+    ) -> list[dict[str, Any]]:


I think we can ? It looks like we know what's going to be in the request data for that serializer so we could type the return here.

Christinarlong · 2024-12-19T21:20:01Z

src/sentry/sentry_apps/api/serializers/sentry_app_webhook_request.py

+    def serialize(
+        self, obj: BufferedRequest, attrs: Mapping[Any, Any], user: Any, **kwargs: Any
+    ) -> SentryAppWebhookRequestSerializerResponse:
+        organization = attrs.get("organization")
+        response_code = obj.data.response_code
+
+        data: SentryAppWebhookRequestSerializerResponse = {
+            "webhookUrl": obj.data.webhook_url,
+            "sentryAppSlug": self.sentry_app.slug,
+            "eventType": obj.data.event_type,
+            "date": obj.data.date,
+            "responseCode": response_code,
+        }
+
+        if organization:
+            data["organization"] = {"name": organization.name, "slug": organization.slug}


Also we're potentially missing the error response & request bodies from error webhook requests here

Same in the RpcModel

We decided to remove some properties for now since they're not shown on the dashboard, we can add them back later if needed

uh can you link me to this discussion ? We shouldn't or we should log them instead since we & customers use that data a lot as a debugging resource

hmm, do we have customer stories where they inspect the response we are sending rather than the dashboard?

I think the conversation was on Slack but #81267 (comment)

Yes, for this customer issue we needed to see our req bodies to validate our webhooks were working. It's also a customer request in this issue. It's currently not a priority to add the UI to the dashboard but without returning at all to the frontend there is no visibility into the buffer for both customers and us.

cc @GabeVillalobos

The general guidance I've been giving @ameliahsu is: exclude it until we actually implement this feature. It should be trivial to add to the response body in the future, but I don't want to be exposing this data right now if we aren't using it. It also gives us an opportunity to analyze the overall performance of this endpoint with smaller payloads to start before adding a bunch of additional data.

clarification q, is 'this feature' == the endpoint ? or the UI ? Either way though, I still think it's very important to expose that data for debugging. The comment 2 up, sums up the reasons and related issues/asks. Without this data being exposed debugging webhooks & buffer issues becomes incredibly hard without setting up an integration on that sentry app's org.

Ah I missed that. Fair point, alright let's go ahead and add it then (sorry @ameliahsu)

Christinarlong · 2024-12-19T21:27:18Z

src/sentry/sentry_apps/api/serializers/sentry_app_webhook_request.py

+        organizations_by_id = {organization.id: organization for organization in organizations}
+
+        return {
+            item: {


also is there a reason we need this nesting?
i.e {item: { org: Org}} vs {org:Org}

qood question -
Looking at the code, the nesting structure {item: {"organization": org}} is necessary because of how Django's serializer system works. Here's why:

The get_attrs() method is part of Sentry's Serializer base class pattern, where:

It needs to return a mapping of objects to their attributes

These attributes are then passed to the serialize() method as the attrs parameter

Each object in item_list needs its own set of attributes
If you were to return just {org: Org}, you would lose the connection between which organization belongs to which item in the item_list, and the serialize() method wouldn't know which organization to use for each object being serialized.
You can see this in how the data is used in the serialize() method:

def serialize(self, obj: Any, attrs: Mapping[Any, Any], user: Any, **kwargs: Any) -> Mapping[str, Any]: organization = attrs.get("organization") # This comes from the nested structure # ... rest of the serialization logic ...

The nesting pattern {item: {attributes}} is a common pattern in Django-style serializers as it maintains the relationship between objects and their associated data throughout the serialization process.

--- from ChatGPT

getsantry · 2025-01-11T08:00:41Z

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

new control endpoint

99e689f

ameliahsu requested review from a team as code owners December 4, 2024 18:14

github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 4, 2024

cathteng reviewed Dec 4, 2024

View reviewed changes

BORKED

baa6ceb

vercel bot deployed to Preview December 5, 2024 18:37 View deployment

ameliahsu added 2 commits December 5, 2024 15:18

omg its working

7c02538

filter and append

a117f74

ameliahsu force-pushed the mia/sentry-app/v2 branch from 3c9862c to a117f74 Compare December 5, 2024 23:44

vercel bot deployed to Preview December 5, 2024 23:49 View deployment

GabeVillalobos reviewed Dec 5, 2024

View reviewed changes

helper methods

c2d8951

github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 6, 2024

ameliahsu requested a review from GabeVillalobos December 6, 2024 22:21

vercel bot deployed to Preview December 6, 2024 22:25 View deployment

ameliahsu changed the title ~~chore(sentry app): new SentryAppRequestsEndpointV2 control endpoint~~ chore(sentryapp): new SentryAppWebhookRequestsEndpoint control endpoint Dec 6, 2024

move filter methods

135705a

vercel bot deployed to Preview December 6, 2024 23:52 View deployment

iamrajjoshi reviewed Dec 18, 2024

View reviewed changes

src/sentry/sentry_apps/api/endpoints/sentry_app_webhook_requests.py Show resolved Hide resolved

iamrajjoshi requested a review from a team December 18, 2024 17:05

Christinarlong reviewed Dec 18, 2024

View reviewed changes

sentaur-athena reviewed Dec 19, 2024

View reviewed changes

GabeVillalobos reviewed Dec 19, 2024

View reviewed changes

typing + new filtering

e1aa641

vercel bot deployed to Preview December 19, 2024 20:43 View deployment

more detailed tests

e2a69d4

vercel bot deployed to Preview December 19, 2024 20:58 View deployment

fix mypy error smh

d012277

vercel bot deployed to Preview December 19, 2024 21:07 View deployment

Christinarlong reviewed Dec 19, 2024

View reviewed changes

getsantry bot added the Stale label Jan 11, 2025

	serializer = ApiTokenSerializer(data=request.data)

	if serializer.is_valid():
	result = serializer.validated_data

		if "start" in data and "end" in data and data["start"] > data["end"]:
		raise serializers.ValidationError("Invalid timestamp (start must be before end).")

		from sentry.sentry_apps.models.sentry_app import SentryApp


		class RequestSerializer(Serializer):

	serialize_rpc_sentry_app_request(req)
	for req in control_buffer.get_requests(event=event, errors_only=errors_only)

chore(sentryapp): new SentryAppWebhookRequestsEndpoint control endpoint #81676

Are you sure you want to change the base?

chore(sentryapp): new SentryAppWebhookRequestsEndpoint control endpoint #81676

Conversation

ameliahsu commented Dec 4, 2024

codecov bot commented Dec 4, 2024 • edited Loading

Codecov Report

cathteng left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot commented Dec 6, 2024

codecov bot commented Dec 6, 2024 • edited Loading

Bundle Report

iamrajjoshi left a comment

Choose a reason for hiding this comment

Christinarlong left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sentaur-athena left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ameliahsu Dec 19, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

iamrajjoshi Dec 19, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

getsantry bot commented Jan 11, 2025

chore(sentryapp): new `SentryAppWebhookRequestsEndpoint` control endpoint #81676

chore(sentryapp): new `SentryAppWebhookRequestsEndpoint` control endpoint #81676

codecov bot commented Dec 4, 2024 •

edited

Loading

codecov bot commented Dec 6, 2024 •

edited

Loading

ameliahsu Dec 19, 2024 •

edited

Loading

iamrajjoshi Dec 19, 2024 •

edited

Loading