JIRA Triggered Cloud Management
Jira Triggered Cloud Management
What if cloud management were as easy as raising a JIRA ticket? Almost every DevOps team uses JIRA as a standard means of issue tracking & task management. It’s a given that it would be a seamless process if you could also integrate your cloud processes with it. We’ve seen a ton of our customers prefer using an integrated approach to their cloud & workflows.
Normally, once a ticket is raised with any issue, an engineer is manually assigned to resolve that task — but what if you could have a virtual DevOps engineer instead? He’d mimic the exact process that a human engineer would do — very intuitively, but with complete automation — that’s the impact of using a TotalCloud workflow, that’s triggered by JIRA. Automation of tasks is always a key element in any DevOps team, and more so when the automation is linking all your tools together, in this case by simply raising a JIRA ticket. This maximizes work efficiency & DevOps productivity.
How It Works
Since we work with workflows, there’s no need to write a single line of code for such an integration — it’s already available through a simple webhook integration. Since workflows are automated, you need to define a ‘trigger’, an instruction for when it needs to run (which can be in response to an event, an alarm, at a set time, or from an external application — in this use case, JIRA. You’re basically telling the workflow to execute automatically when a JIRA ticket gets raised with the matching summary.
What that workflow does, can be any possible AWS action imaginable.
The extent of the actions & automation you can do
You can apply this concept across any possible AWS automation or action. You can create major changes in the nature of your infrastructure, or simply pull basic monitoring data, or deploy an entire infrastructure.
You will be capable of managing-
- Simple cloud operations
- Scheduled alerts
- Changing the state of your instances
- Infrastructure management
- Create an infrastructure
- Deploy certain services
- Provision resources
The most common use case — auto-remediation from JIRA
Auto-remediation is a sought after feature when you’re trying to maintain the performance efficiency of your cloud. Let’s say a server’s CPU utilization has exceeded 90%, it’s natural for the server to slow down. Normally, it’s fixed manually — which means there’s a higher response time & effort needed. In the case of a JIRA-integrated workflow especially — the moment an erroneous event occurs, the JIRA ticket will act as an automated event-response, in real-time. We’ve seen companies have multiple DevOps engineers just to respond to tickets & errors, which can all just be automated.
If you want to automate the process end-to-end- you can have the workflow raise a JIRA ticket when a CloudWatch alarm goes off, the corrective action then executes, and the workflow then closes the ticket. The workflow can pretty much be a virtual DevOps engineer.
A simple example of this would be a case where you need to reboot services. To reboot your apache server in case of it going unresponsive, you can raise the ticket and the workflow will trigger the response. If you have a CloudWatch alarm that detects high usage, that can be the start of the flow — which will raise a ticket & run the workflow. It’s mimicking what a DevOps engineer would normally do, but fully automatic.
We’ve seen some extremely common auto-remediations used by our customers, so we’ve templatized them — to be adopted in a single click. Let’s deep dive into three such flows. In this example, we are approaching the issue of high CPU utilization with three different solutions. I will explain the process and show how the workflow functions.
- Jira Triggered Instance Reboot
- Jira Triggered Instance Reboot Process
- Jira Triggered Instance Upgrade
Jira Triggered Instance Reboot
Rebooting the instance by raising a Jira ticket. Mention the tag in the ticket description to have the specified machines be rebooted. This can be used when a specific machine’s CPUUtilization goes high. Rebooting can reduce utilization.
Jira Triggered Instance Process Reboot
Rebooting 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 CPUutilization. The trigger is the tags specified in the Jira Ticket description.
Jira Triggered Instance Upgrade
Upgrading the instance to a higher spec machine by raising a ticket. When the CPUutilization is high, the server/application demands an upgraded machine to handle the workload. Trigger a machine upgrade by specifying the tags in the Jira Ticket description.
Instance upgrade is also a rightsizing solution. By raising JIRA ticket, the workflow rightsizes your machines to match your higher workload demand.
Cloud management can get exponentially easier when you harness the potential of workflows over scripting. Use Totalcloud to find creative solutions to common complicated use cases.