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

Incident status not changing on new events #321

Open
ghesla-mumms opened this issue Mar 21, 2024 · 1 comment
Open

Incident status not changing on new events #321

ghesla-mumms opened this issue Mar 21, 2024 · 1 comment

Comments

@ghesla-mumms
Copy link
Contributor

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.

@piotr-szewczyk
Copy link
Collaborator

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
- 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'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants