Welcome to the Cortex blog

Integrating Bugsnag into Cortex can help users monitor application stability.

Remote work is here to stay - here's 6 tips you can use to build a great onboarding process and make your engineering team more cohesive and productive as a result.

Integrating GitLab into Cortex can help teams import services easily, view Git commits alongside other events in the service timeline, and monitor development maturity using Scorecards.

With the growth of the SRE role, we're exploring a few key SRE principles that we believe apply strongly across functions and all engineering teams would benefit from adopting.

Integrating SonarQube into Cortex can help users monitor code quality & security through Scorecards.

We've all dreamed of going viral and seeing usage skyrocket overnight but how do we actually prepare for that moment?

Integrating Sentry into Cortex can help users monitor service issues.

Keeping track of service ownership across all microservices is extremely important but how should teams self-organize to achieve it and where's the best place to start?

On paper, being an SRE may look nothing like being in sales. But in reality, and especially if you work for a startup, there’s more overlap than you might think. Learn four ways you can improve your influence within the engineering team as a SRE!

Cortex integrates with Snyk to help map vulnerabilities to services in the catalog and monitor vulnerabilities using Scorecards.

The move from a monolith to a microservices/service-oriented architecture can be daunting. In this post we'll be going over five things to keep in mind that we’ve learned from helping teams navigate this transition.

We see teams fall into a few common traps with SLOs, SLIs, and SLAs, particularly when they’re just starting out. In this article, we’ll first define these three acronyms (it’s easy to get confused!) and show you how to avoid the mistakes other teams make.

What does your team’s production readiness practice look like for deploying a new service? If you or a dedicated SRE team within your engineering organization has ever green-lit a new service, you probably have used some form of a production readiness checklist to ensure certain conditions are met and processes are followed. In this article, we’ll share some helpful approaches for creating a great production readiness checklist that will set your team up for a successful launch.

Your on-call system is vital to business—you must be able to help customers fix issues as fast as possible.But being on-call can stress out your employees. A poor on-call rotation can magnify this issue, leaving your employees drained and stressed out.

Kubernetes, also known as k8s, is an open-source system for managing containerized applications. Since its introduction in 2014, Kubernetes has revolutionized modern application building towards containers and microservices.

These days, many software teams use microservices to build applications because they offer increased flexibility and scalability.But by solving one problem, you now have to contend with another: How do you keep track of all your microservices?

SREs are responsible for evaluating tools that can help reduce toil on their teams and make their applications more reliable for end-users. There are a lot of SRE tools out there, and it can be hard to know which ones are the most important to consider. We’ve compiled this guide to highlight the key categories of SRE tools and help you find the right fit for your team.

The objective of this article is to provide an introduction and a general understanding about Kubernetes. We will look into architectural concepts, advantages of using Kubernetes, how to set up Kubernetes, and how to run commands on a local machine using Minikube.

Historically, development teams and operations teams have been at odds.

Historically, development teams and operations teams have been at odds.

Digital transformation means enterprises have to embrace new ways of thinking—from how they structure their teams to their application architecture.

Organizations that operate microservices/service-oriented architecture face a variety of technical and people related problems.

Historically, development teams and operations teams have been at odds.