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

Realtime alerts should group whenever possible #3102

Open
mlissner opened this issue Sep 5, 2023 · 6 comments
Open

Realtime alerts should group whenever possible #3102

mlissner opened this issue Sep 5, 2023 · 6 comments
Assignees

Comments

@mlissner
Copy link
Member

mlissner commented Sep 5, 2023

I signed up for real time alerts for all oral arguments, and today I got three emails at almost exactly the same time because we scraped three items from the DC circuit all at once. Instead of doing that, we should send one alert with all three.

This will become more important as we move to RECAP, because we'll be getting dozens or even hundreds of docket entries at a time, and we should be sure we only send one email when that happens.

One solution is to delay RT alerts by a few minutes, but that's pretty unsatisfying (this is how Stackoverflow does it, but still). If we can, we should try to be smarter about how we send. Some of our users insist that ever second counts.

@albertisfu
Copy link
Contributor

This is done for RECAP in #4200 I'll use this issue to apply grouping also for Oral arguments RT alerts.

@mlissner
Copy link
Member Author

To be clear, I think this applies across all RT alerts, no?

@albertisfu
Copy link
Contributor

Yeah, that's correct. For now, we need to apply it to Oral Argument RT alerts, which is the other document type supported by the Percolator.
Opinions Alerts will continue using the current cl_send_alerts approach, with the difference of using Elasticsearch (instead of Solr) to query alerts. There grouping is already applied for RT alerts. We'll need to consider grouping for Opinions Alerts once we move them to the Percolator/Sweep index approach which I don't think we have an issue for that yet. Should we create one?

@mlissner
Copy link
Member Author

Yep, let's get on it. :)

@albertisfu albertisfu moved this from 📋 Backlog to 🏗 In progress in @albertisfu's backlog Jul 26, 2024
@s-taube s-taube moved this to Sprint: Nov 25- Dec 6 in Sprint Planning Backlog Nov 5, 2024
@s-taube s-taube added this to Sprint Nov 14, 2024
@s-taube s-taube moved this to Backlog Nov 25 - Dec 6 in Sprint Nov 14, 2024
@s-taube s-taube closed this as completed Nov 25, 2024
@github-project-automation github-project-automation bot moved this from Backlog Nov 25 - Dec 6 ( 💀 ➡️ ☀️ ) to Done in Sprint Nov 25, 2024
@github-project-automation github-project-automation bot moved this from RECAP Alerts to Done in Elastic Search Launch Nov 25, 2024
@s-taube s-taube reopened this Nov 25, 2024
@s-taube s-taube moved this from Done to In review in Sprint Nov 25, 2024
@mlissner
Copy link
Member Author

What are we holding this open for?

@albertisfu
Copy link
Contributor

Yes, this is still open since the review of #4251 is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

No branches or pull requests

3 participants