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

Slack notification delay after new issue arrived to sentry #2034

Closed
maylow opened this issue Mar 17, 2023 · 3 comments
Closed

Slack notification delay after new issue arrived to sentry #2034

maylow opened this issue Mar 17, 2023 · 3 comments

Comments

@maylow
Copy link

maylow commented Mar 17, 2023

Self-Hosted Version

23.3.0

CPU Architecture

x86_64

Docker Version

20.10.5

Docker Compose Version

2.16.0

Steps to Reproduce

  1. Upgrade Sentry to 23.3.0

  2. Create alert to send slack notification when new issue is created.

  3. Send issue via sentry-cli.

  4. Sentry gets an issue but not mark it as new issue for 5 minutes.
    sentry_issue

  5. After 5 minutes, it gets mark new issue and send issue to slack.

slack_info

Expected Result

  1. Create alert to send slack notification when new issue is created.
  2. Send issue via sentry-cli.
  3. Sentry gets an issue, mark it as new issue and send it to slack.

Actual Result

We have 2 versions of sentry:

  1. 22.10.0 - It is working as expected. New issue send notification to slack immediately.
  2. 23.3.0 - It stop working after upgrade. Issue gets mark new issue after 5 minutes.
    sentry_issue

slack_info

I didn't find anything wrong in logs.
Also, this sentry doesn't have real traffic since this is just testing dev sentry. We are sending there a few issues per hour.
Any help would be appreciated.

Event ID

No response

@hubertdeng123
Copy link
Member

I believe this is a duplicate of #1982

The alert won't trigger immediately and the offset is lagging by 1. Can you confirm this is the case?

@maylow
Copy link
Author

maylow commented Mar 20, 2023

Hello @hubertdeng123 , yes, seems like duplicate with different time delay.

@hubertdeng123
Copy link
Member

thanks, closing this then since our team is aware of this and investigating

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants