-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update historic incident api to include root cause incident message #5134
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
base: master
Are you sure you want to change the base?
Update historic incident api to include root cause incident message #5134
Conversation
Hi @kmannuru , |
@HeleneW-dot I've attached the issue related to the change. #2697. Please help review when you get a chance. Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kmannuru ,
Thanks for linking the ticket and picking up this feature request 💪
I have now finally had time to review the PR.
I have reviewed the changes and locally tested them and it looks good!
I only have one requets which is to add more test cases, specifically cases that cover real deployment data where a model is deployed, incidents are created and then we check that the query retrieves the correct incident data. At the moment the added test cases are only asserting on mocked responses.
You can have a look at existing test cases in HistoricIncidentTest
as examples here.
Summary:
👍 Reviewed code changes look good
👍 openAPI updates included
👍 Manually tested by me locally
👍 CI: QueryTests exist on mocked incident responses
🚫 CI: No test for real deployment data.
🚫 PR CI: I think I have to duplicate the branch to run the PR CI jobs. @HeleneW-dot will do this do next once changes have been implemented
@@ -388,23 +388,29 @@ | |||
<result property="removalTime" column="REMOVAL_TIME_" jdbcType="TIMESTAMP"/> | |||
</resultMap> | |||
|
|||
<resultMap id="historicIncidentResultWithRootCauseIncidentMessageMap" type="org.camunda.bpm.engine.impl.persistence.entity.HistoricIncidentEntity" extends="historicIncidentResultMap"> | |||
<result property="rootCauseIncidentMessage" column="ROOT_CAUSE_INCIDENT_MESSAGE_" jdbcType="VARCHAR"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick:
to keep consistent and short lets also abbreviate message
here like in the other message field:
<result property="rootCauseIncidentMessage" column="ROOT_CAUSE_INCIDENT_MESSAGE_" jdbcType="VARCHAR"/> | |
<result property="rootCauseIncidentMessage" column="ROOT_CAUSE_INCIDENT_MSG_" jdbcType="VARCHAR"/> |
Hi @kmannuru , |
Issue: #2697