-
Notifications
You must be signed in to change notification settings - Fork 626
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
[Feature Request] Keep sourceRef with case #744
Comments
With the changes in #687 this is something that might be able to be done with custom fields if we were able to add custom fields into the Alert and have them carry over to the case. |
This is possible, when your define a custom field in an alert, it's copied to the case. I'll close the issue, and please feel free to reopen it if needed. |
Yup that worked! Thanks! There was no API documentation about customFields in alerts and it wasnt in theHive4py so i was not aware that this could be done |
@nadouani |
Request Type
Feature Request
Request
It would be very helpful to keep the sourceRef(s) with the case when an alert is turned into a case. This would be useful in cases where you would like to call a webhook and respond to the service that generated the alert.
for example if PagerDuty generated an alert with sourceRef = 123abc When that alert is turned into a case I would like to acknowledge it in PagerDuty and when its closed i'd like to resolve it in PagerDuty. However as soon as the case is created i lose the sourceRef
Possible Solutions
store and object in the case of
sourceRefs=[{source:sourceRef}]
so for examplesourceRefs=[{"pagerduty":"123abc"}]
This would work with multiple alerts merged into one case
The text was updated successfully, but these errors were encountered: