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

[ResponseOps][Actions] Research how we can persist information related to resources in external services #208302

Open
cnasikas opened this issue Jan 25, 2025 · 1 comment
Labels
Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@cnasikas
Copy link
Member

cnasikas commented Jan 25, 2025

Rules, through actions, can interact with external services like ServiceNow or Jira. Incidents or issues can be opened in this service when an alert is triggered. Some services offer mechanisms where you can refer to the resource created in the external service and update or delete it. This is not possible in some cases, like Jira or OpsGenie. It became apparent that to support any external service, we would need to persist in information about the resource created in the external service to be able to interact with the resource. We should gather requirements, research, and propose solutions that will aid us achieve our goal.

DoD

  • Gather requirements and user scenarios
  • Research and propose a solution

Related: https://github.com/elastic/enhancements/issues/22592, #173274, #162557

@cnasikas cnasikas added Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 25, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework research Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

2 participants