Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(inbound-filters): Add react hydration errors filter to frontend #45300

Merged

Conversation

priscilawebdev
Copy link
Member

Frontend

Preview:

image

@priscilawebdev priscilawebdev requested a review from a team March 2, 2023 10:08
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 2, 2023
jan-auer and others added 7 commits March 2, 2023 11:26
Adds an ingest consumer similar to Replays and Profiles that reads from
a Kafka topic `ingest-monitors` and updates them directly in postgres.
The consumer runs automatically in devserver and can be started via
`sentry run ingest-monitors`.

This supports creating and updating check ins with a status and
duration. Creating monitors is not supported yet. The consumer closely
follows the logic from checkin creation, but there is a difference for
disabled monitors compared to the Update (PUT) endpoint.
…at/add-react-hydration-errors-inbound-filter-frontend
Base automatically changed from feat/add-react-hydration-errors-inbound-filter to master March 3, 2023 08:07
@priscilawebdev priscilawebdev requested a review from a team March 3, 2023 08:07
@priscilawebdev priscilawebdev merged commit eba4f0c into master Mar 3, 2023
@priscilawebdev priscilawebdev deleted the feat/add-react-hydration-errors-inbound-filter-frontend branch March 3, 2023 08:36
@github-actions github-actions bot locked and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants