Allow additional ServiceNow fields #1668
Locked
mitchell-es
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Yes, please submit a PR with these changes. I prefer to avoid breaking changes and there's no harm in having the existing, explicit fields available for users to make use of. The Please change these lines:
to:
Also review the contribution guidelines and make sure all the requirements are meant. The PR will also display a list of checkboxes you'll need to check off before it can be merged. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have a need in our environment to set an additional field for the created incidents. It happens to be a custom field so I don't expect elastalert2 would ever support it directly so I took a page from the Jira alerter and allowed specifiying additional fields with a 'servicenow_arg_' prefix. I've got a branch with the changes and it passes the unit tests and has updated docs. This would be my first time submitting a PR to this project so I figured I'd check in first see if anyone had thoughts on it.
Specifically, is the chosen prefix OK or is there something that would work better? Also, the new syntax would actually allow removing most of the existing options for the rule as they can all be specified using the new syntax. But that would either break existing configurations or require a lot of extra code to manage both the 'new' and 'old' style so I did not invest any time going down that path. I'm happy to do that work but only if the community would find it valuable.
Anyway, the branch can be seen at https://github.com/mitchell-es/elastalert2/tree/allow_additional_servicenow_fields Feedback is welcome. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions