Operations | Monitoring | ITSM | DevOps | Cloud

Jira Automation Demystified

Repetitive tasks can be time consuming. In an ideal world, automation would remove all of the grunt work when it comes to solving business problems, freeing us up to execute on more strategic decisions. Luckily, Jira has the capabilities to take a load of tasks off your hands – including tracking your issues, posts, features, and more. This blog will walk you through the options available and offer top tips on how to set this up.

Dashboard Fridays: Zendesk

This Zendesk dashboard built in SquaredUp provides an overview of the support tickets that have been raised in Zendesk, information on tickets created, against which form, what status they are in, and how many when taken by users. Tune in to learn how it was made, the challenges it solves, and our top tips for building it yourself.

Dashboard Fridays: Azure DevOps

This SquaredUp dashboard uses the Azure DevOps plugin to let you monitor the status of your CI/CD automation, monitor Azure DevOps for failures and large queues, track the usage of your agents and resources, and summarise work items and test cases. Tune in to learn how it was made, the challenges it solves, and our top tips for building it yourself.

SLO walkthrough: measuring microservice performance

To improve reliability, we need to measure it, and to measure it we use SLOs (Service Level Objectives). Or at least, that’s what Google SRE has popularized. In practice, it can be difficult and time-consuming to identify the right things to measure, to get to the right data, and to surface the results in a way that engages the stakeholders and teams involved. And all this is especially hard as we scale our teams and applications across multiple technology stacks.

Incident response: Unlocking knowledge and breaking down silos

In a world of monolithic applications and microservices, responding to incidents can be a painful process, involving multiple people with siloed knowledge jumping between different tools to find the relevant data and take action. Individuals within a business often hold the knowledge of how a particular component works, or how it depends on other services. The key to successfully responding to incidents is unlocking this knowledge and breaking down the silos between teams.