Operations | Monitoring | ITSM | DevOps | Cloud

The year 2021 has ended, and we are now entering 2022. Last year, Microsoft released a few new Azure services and updated others. This blog post will discuss the most exciting cloud integration-related updates and releases.

Last week I created a guide for our users to set up an NGINX service as an API Gateway with Qovery. The API gateway must redirect the incoming traffic to the appropriate service with the correct port. My problem is that the API Gateway does not know the ports exposed for every service. In this post, I will show you a quick tip on finding the port of a Kubernetes service with a single DNS request. Let's go!

It’s an exciting day at Sysdig as we announce our channel-first approach to doing business. What does this mean exactly? Going forward, we will be conducting sales for all customers outside of the Global 500 through a channel partner. For more than three decades, customers have leveraged channel partners as trusted advisors for vendor-agnostic IT consultation and expertise. Our channel-first approach moves Sysdig in line with how customers buy.

A huge challenge when dealing with incidents is the coordination and communication needed to put things right. What’s happened so far? Who has tried what query? Did we remember to keep stakeholders informed? What is the severity of the incident? Does this affect customers? Figuring this out requires a lot of back and forth as new team members join the incident.

Speedscale is excited to join the AWS Partner Network (APN), the global community of partners who leverage Amazon Web Services (AWS) to build solutions and services for customers. AWS Partners are uniquely positioned to help businesses take full advantage of all that AWS has to offer and accelerate the journey to the cloud. As part of this achievement, Speedscale has completed the AWS Foundational Technical Review (FTR).

Cloud computing is vast. It encompasses a huge range of architectural styles, classifications, and types. This complex computing network has transformed the way we work and is a crucial part of our daily lives, both at home and at work. For organizations, there are many ways to “cloud”, but let’s start with the basics of cloud computing; the internet cloud.

CircleCI cloud offers over 20 resource classes (varying CPU and RAM) across multiple execution environments. Finding the best resource class size for your job — not too big and not too small — can sometimes be a challenge. But now, you can view CPU and RAM usage for Docker executors within the UI. The new dashboard, found in the new Resources tab on the job details page, displays the CPU and RAM, for all parallel runs in your Docker job.

For the past three years, I have been running and facilitating a community where folks from all levels and departments at CircleCI can come together to discuss diverse topics. We call it “Let’s Talk Engineering.” Some of the topics we’ve covered have been technical in nature, while others have focused more on leadership: how different teams operate, personal growth, and writing to name a few. Let’s Talk Engineering celebrates interdisciplinarity and multidisciplinarity.

Before we talk about OpenTelemetry, we should talk about telemetry. Telemetry is: And an instrument is: For the purpose of measuring running computer software and systems, our instruments are virtual instruments. That is to say, code that measures other code. It sounds simple: read a measurement and send it to a remote location. In practice, to make that telemetry data useful in today’s cloud-native and ever more complex environments, there are huge logistical and technical hurdles to overcome.

OpenTelemetry is enabling a revolution in how Observability data is collected and transmitted. See our What Is OpenTelemetry post on why this is an important inflection point in the Observability space. In this post, we’ll walk through how to configure the OpenTelemetry Gems within a Rails app.