Operations | Monitoring | ITSM | DevOps | Cloud

CI/CD is the process that ensures that code updates are deployed efficiently and reliably. However, more than simply having CI/CD pipelines is required for modern business application development needs. The problems start as soon as your team grows, but your CI/CD process does not. Static CI/CD pipelines result in an operational bottleneck and slow down your application workflow. Today, we will discuss why scaling your CI/CD is an inevitable need for your organization.

It feels like everything is getting a “smart” upgrade these days. From the cars we drive to how we operate our domestic appliances, almost every gadget has had a smart upgrade or now uses Artificial Intelligence (AI) to improve our lives – or so they claim…

Errors are part of building software. Even if you are one of the fabled 10X engineers, errors are still going to happen. When an error does occur, typically you are going to look at the stack trace to understand the why and who for triaging. But figuring out who to assign an issue to just based on the stack trace can be difficult. How many times do you see a stack trace in a Sentry issue, head to GitHub, and try to figure out who changed the line of code in question? Often would be our guess.

You build it; you own it! It’s a simple mantra that has driven software development for years. The days of writing software and throwing it over the wall to operations teams are over. Instead, software development teams take ownership of what they do and own their own software operations. There is just one problem: Monitoring tools have not yet adopted the developer workflow. As a developer, the repository is the center of the workflow. It's the one single source of truth.

NetApp, formerly Network Appliance Inc., is a computer technology company specializing in data storage and management software. NetApp provides cloud data services, primarily for the management of data. It also offers management solutions for applications.

The DevOps pipeline is a crucial part of software development, but it can often get mired in bottlenecks. Most problems are caused by the development and operations teams having different responsibilities are due to inefficiencies in the pipeline design. However, thanks to continuous observability, DevOps now gets a new lease of life since it is possible to tweak the pipeline to suit the developer’s workflow.

We all know about the great things Grafana dashboards can do, and configuring them as code makes it possible to get even more out of them. These days, Grafana resources can mostly be managed as code in a declarative manner, which enables code review, code reuse, and in general, better workflows. This guide presents a few as code tools you can use to declaratively manage Grafana resources, plus some tips and tricks on how to incorporate them efficiently into your own use cases.