.svg)
.svg)
What if managing your instances were as easy as raising a JIRA ticket? Almost every DevOps team uses JIRA as a standard means of issue tracking & task management. We’ve seen a ton of our customers prefer using an integrated approach to their cloud & workflows. Hence, we’ve adopted a workflow for easier management of instance states through JIRA triggers.
To automate the process end-to-end- the workflow raises a JIRA ticket when a CloudWatch alarm goes off, the corrective action then executes, and the workflow then closes the ticket. The workflow acts as a virtual DevOps engineer. The action here would be rebooting the instances when an alarm for high CPU utilization goes off. See the detailed workflow docs here.
Reboot the process associated with a machine by raising a ticket. The Apache servers associated with the EC2 machines will be rebooted when it causes high CPU utilization(set threshold as per your need). The trigger is the tags specified in the Jira Ticket description. The workflow will create a Jira ticket when the CloudWatch alarm alerts of high CPU utilization and then after the machines reboot, the ticket is closed before the workflow ends.
Use this to initiate a workflow based on time, events or call.
.svg)
Use this node to execute custom business logic.
Select resources on which you want to work on.
Enter parameters to filter resources in the workflow.
Use this to get approval from stakeholder to continue the workflow.
Select action to be done on resources in the workflow.
Use this to initiate a workflow based on time, events or call.
Use this node to execute custom business logic.
Select resources on which you want to work on.
Enter parameters to filter resources in the workflow.
Use this to get approval from stakeholder to continue the workflow.
You can publish templates created by you on this platform.
.svg)
