-
Notifications
You must be signed in to change notification settings - Fork 15
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
Incident status not changing on new events #321
Comments
Hi! Thanks for this issue, i will take a look at this. If you want you can also open a PR with a fix. Thanks in advance! |
ghesla-mumms
added a commit
to ghesla-mumms/traceo
that referenced
this issue
Mar 22, 2024
- reset incident status when new event is received - use 82905 pattern in criteria when querying incidents by name, project_id, and message to 'avoid issues with escaping both single and double quotes'
piotr-szewczyk
pushed a commit
that referenced
this issue
Mar 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Great job on this project! This ticks a lot of boxes for a project I'm working on.
The documentation states:
"Unresolved - status set automatically when a new incident is created or when a new event is received for a given incident"
However, in our testing, this is not the case. Existing incidents that have been marked as "Resolved" do not get reset to "Unresolved" status.
I have set up the project locally using the Dockerfile, and everything appears to be running normally. I have not seen any errors or log messages that would indicate an error.
I'll try and drum up a fix for this and submit a pull request.
The text was updated successfully, but these errors were encountered: