Skip to content

feat(ACI): Add documentation for OrganizationDetectorIndexEndpoint GET#106025

Merged
ceorourke merged 4 commits intomasterfrom
ceorourke/document-OrganizationDetectorIndexEndpoint-GET
Jan 12, 2026
Merged

feat(ACI): Add documentation for OrganizationDetectorIndexEndpoint GET#106025
ceorourke merged 4 commits intomasterfrom
ceorourke/document-OrganizationDetectorIndexEndpoint-GET

Conversation

@ceorourke
Copy link
Copy Markdown
Member

@ceorourke ceorourke commented Jan 9, 2026

Add documentation for the GET OrganizationDetectorIndexEndpoint.

This will not be published yet, but in order to deploy the workflow engine API documentation in pieces we'll set the publish_status to PUBLIC all at once and add the sidebar item for workflow engine.

Screenshot 2026-01-09 at 12 39 40 PM

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 9, 2026
@ceorourke ceorourke marked this pull request as ready for review January 9, 2026 21:27
@ceorourke ceorourke requested review from a team as code owners January 9, 2026 21:27
Copy link
Copy Markdown
Member

@malwilley malwilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a great start!

owner: str | None
createdById: str | None
owner: ActorSerializerResponse | None
createdBy: str | None
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@malwilley was createdById being used in the UI?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think createdById was ever being returned, it only exists on this serializer type. We use createdBy on the frontend

createdBy: string | null;

dateUpdated: datetime
dataSources: list[dict]
conditionGroup: dict
dataSources: list[dict] | None
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should dataSources allow for None? I think it'd fine o the processing side, just not sure if we have any existing use cases for not having a data source on a detector rn.

Copy link
Copy Markdown
Member Author

@ceorourke ceorourke Jan 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Error monitors have a data source of None - I guess from a user perspective (since they won't be making those) it must always have one though. Let me see if I can remove it without the API docs tests failing.

@ceorourke ceorourke merged commit f0ad18a into master Jan 12, 2026
66 checks passed
@ceorourke ceorourke deleted the ceorourke/document-OrganizationDetectorIndexEndpoint-GET branch January 12, 2026 17:44
ceorourke added a commit that referenced this pull request Jan 20, 2026
…t POST (#105882)

Follow up to #106025 to add
documentation for the POST `OrganizationDetectorIndexEndpoint`.

This will not be published yet, but in order to deploy this in pieces
we'll set the `publish_status` to `PUBLIC` all at once and add the
sidebar item for workflow engine.

The POST endpoint handles multiple detector types with various
additional body params which isn't supported in our API documentation
(it expects a single serializer), so I've done something similar to how
we document the [issue alert creation
endpoint](https://github.com/getsentry/sentry/blob/master/src/sentry/api/endpoints/project_rules.py#L282).
This will need updating if we add more detector types, but unless the
documentation framework is changed to support multiple serializers this
is the best we can do.

<img width="2692" height="15998"
alt="localhost_3000_api_workflows_create-a-monitor-for-a-project_"
src="https://github.com/user-attachments/assets/e2fcfdf7-0020-44c1-a4e2-7bd6b0bf6fc9"
/>
@github-actions github-actions bot locked and limited conversation to collaborators Jan 28, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants