-
Suggestion
-
Resolution: Unresolved
User Problem
In the current design, the Action Filter of every integration on Opsgenie can only select the pre-defined fields which may limit the flexibility of usage.
In reality, the payload structure could be customized and different across different scenarios/instances.
It would be ideal to support using Regex in the Filter to capture the wanted fields.
Suggested Solutions
Add the Regex support in the Action Filter for capturing the customized fields.
Current Workarounds
Custom fields can still be extracted from the payload and parsed into 1 of the Opsgenie alert fields, using dynamic fields/string processing/regex.
Once you find the dynamic field that extracts the custom field, parse this into one of the create alert action's alert fields - such as an extra property.
You can then use Alert policies to filter on the extra property, and modify the alert to add a responder, add a tag, etc.
- is duplicated by
-
- Gathering Interest
- is related to
-
- Gathering Interest
-
- Gathering Interest
-
- Under Consideration
[OPSGENIE-651] As an admin, I want to use regex or any way on the Filter of Action Filter of an integration to configure the filter with non-predefined fields
| Labels | New: RIBS-SHORT |
| Remote Link | New: This issue links to "Page (Confluence)" [ 924447 ] |
| Assignee | New: Karthik Kalyanasundaram [ 30edc11e864f ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 884073 ] |
| Status | Original: Gathering Interest [ 11772 ] | New: Reviewing [ 11773 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 741018 ] |
| Link | New: This issue is related to OPSGENIE-672 [ OPSGENIE-672 ] |
| Link | New: This issue is related to OPSGENIE-604 [ OPSGENIE-604 ] |
| Link | New: This issue is duplicated by OPSGENIE-869 [ OPSGENIE-869 ] |
| Description |
Original:
h3. User Problem
In the current design, the [Action Filter|https://support.atlassian.com/opsgenie/docs/action-filters-in-opsgenie-integrations/] of every integration on Opsgenie can only select the pre-defined fields which may limit the flexibility of usage. In reality, the payload structure could be customized and different across different scenarios/instances. It would be ideal to support using Regex in the Filter to capture the wanted fields. h3. Suggested Solutions Add the Regex support in the Action Filter for capturing the customized fields. h3. Current Workarounds N/A |
New:
h3. User Problem
In the current design, the [Action Filter|https://support.atlassian.com/opsgenie/docs/action-filters-in-opsgenie-integrations/] of every integration on Opsgenie can only select the pre-defined fields which may limit the flexibility of usage. In reality, the payload structure could be customized and different across different scenarios/instances. It would be ideal to support using Regex in the Filter to capture the wanted fields. h3. Suggested Solutions Add the Regex support in the Action Filter for capturing the customized fields. h3. Current Workarounds Custom fields can still be extracted from the payload and parsed into 1 of the Opsgenie alert fields, using dynamic fields/string processing/regex. Once you find the dynamic field that extracts the custom field, parse this into one of the create alert action's alert fields - such as an extra property. You can then use Alert policies to filter on the extra property, and modify the alert to add a responder, add a tag, etc. |