Checks

Shifting to a microservice architecture comes with well-known benefits. Isolation between systems and teams means feature teams can iterate faster and the entire software engineering organization can scale with more efficiency and agility.

OpsLevel helps keep your services consistent and healthy through the use of various pre-built checks. But what if you want to write your own checks from scratch? You can now do that with OpsLevel custom checks. Our custom checks API opens up endless possibilities, allowing you to do things such as integrating with your deployment pipeline or container orchestrator, writing your own check scripts, and more.

In the rapidly evolving space of internal developer portals (IDPs), two platforms often stand out for their customizability and community support: Port and Backstage. Both offer the promise of creating a tailored internal developer experience, but the path to getting there is fraught with challenges—high setup costs, long implementation times, and excessive complexity. For engineering teams seeking fast, reliable solutions, these platforms may fall short. In this article, we’ll compare Port and Backstage, exploring their pros and cons, and highlighting why OpsLevel offers a more scalable and efficient alternative for organizations looking to improve developer autonomy and streamline service management.

There’s been a notable uptick in engineering teams' adoption of Internal Developer Portals (IDPs) to streamline developer workflows, manage services, and enforce software standards. Two popular options, Cortex and Backstage, offer intriguing approaches to solving these challenges. But as many teams discover, the complexity and limitations of these platforms can outweigh their benefits, especially when scalability, flexibility, and speed are priorities. That’s where OpsLevel comes in. In this article, we’ll explore the pros and cons of Cortex and Backstage, and explain why OpsLevel is the best alternative for engineering teams that want to move quickly, maintain high standards, and minimize operational overhead.

It’s no secret that we all aim for our services to be reliable, scalable, and efficient. But how do you measure whether each of your services is meeting these goals? That’s where Service Maturity Assessments come in. Performing a Service Maturity Assessment helps you evaluate the current state of your services, identify areas for improvement, and ensure consistency across your service ecosystem. Whether you’re managing a handful of services or hundreds, this guide will give you a clear framework for assessing your services and ensuring they are primed for success. In this post, we’ll walk through what a service maturity assessment is, why it’s essential, and how to conduct it step by step. Plus, you can download our free Service Maturity Assessment Template to help you get started right away.

Create checks to track package versions.

All the latest features and updates for OpsLevel released in April.

There’s more pressure than ever on engineering teams to move fast—the ability to adapt and evolve is key to success. But with teams constantly pushing forward, it’s easy to justify shelving service health initiatives. That's where OpsLevel's new Historical Reporting steps in. Our new Historical Reporting functionality helps teams get actionable insights into where their service health stands, what needs to be fixed, and who to tap to take it on. It’s not just about looking back; it’s about gaining the insights you need to propel forward. Let's dive into how Historical Reporting can transform your engineering organization, clarifying your maturity journey.

Here’s a recap of updates and fixes released this month.