Operations | Monitoring | ITSM | DevOps | Cloud

You’ve probably heard something like this before: “It’s a managed service! We don’t need to worry about anything!” But when it comes to your production workloads, database monitoring is imperative. With the new Snowflake Dashboards and Detectors in the Splunk Observability Content Contributors repository you can start seeing the details of individual Snowflakes.

In this tutorial, we'll deploy a simple web app to the cloud of your choice - composed of a database and a virtual machine where the frontend code will run. So that the configuration is reusable and consistent, we'll write it in Terraform. Usually Terraform configurations are cloud-specific, and changing clouds requires a complete rewrite. In this case, so that you can reuse the same configuration across clouds, we'll be using Multy.

Food retailers reduce the workload accumulated by their IT areas by almost 30% thanks to monitoring. Controlling data and extensive information from the whole company, by controlling, supervising and ordering everything through the same system, allows to reduce the times of action in the face of possible errors and failures, improves resource management and organization and increases the effectiveness of the business activity. In addition, monitoring saves costs.

LogSnag is the new kid on the block, but we bet that it will become relevant in this space soon. Today we will show you how to monitor outages and get alerts for your third-party services within LogSnag. What is LogSnag? Here's the intro, but you can learn more at LogSnag official website.

One of the great things about GitFlow is that it makes parallel development very easy by isolating new development from finished work. New development, such as features, is done in feature branches and is only merged back into the main body of code when developers have validated the feature and the code is ready for release. For most development teams, feature validation happens in a staging branch coupled with a single testing environment.

We chose to use GoReleaser with our distro of the OpenTelemetry Collector in order to simplify how we build and support many operating systems and architectures. It allows us to build targeting a matrix of GOOS and GOARCH targets as well as automate creating a wide range of deliverables. Ones we have utilized are building tarballs, nfpm packages, docker images, and Homebrew formula.

Logs are key to monitoring the performance of your applications. Kubernetes offers a command line tool for interacting with the control plane of a Kubernetes cluster called Kubectl. This tool allows debugging, monitoring, and, most importantly, logging capabilities. There are many great tools for SREs. However, Kubernetes supports Site Reliability Engineering principles through its capacity to standardize the definition, architecture, and orchestration of containerized applications.

Ephemeral environments are getting popular among companies that need to scale their business efficiently. Traditionally, the deployment environments usually included development, QA, staging, UAT, and production. However, the bottlenecks with shared QA and staging environments have hindered the efficient workflow of IT teams. The first issue you will face is environment drift because it is a shared environment, and you cannot afford a separate static environment for each developer.

At Qoddi, we are strong advocates and sponsors of open-source projects, and with the recent decision from Heroku to stop offering free plans (used by a lot of open-source developers), we felt the importance of having an alternative ready to keep those projects running. Qoddi's infrastructure is compatible with most of Heroku's buildpacks and we wrote a guide to migrate a project from Heroku.