Blog

Burnout can affect us all, and unless we watch for the causes and signs in our teams and organizations, we may not see it coming until it’s too late.

These days we all feel the pressure of shipping more frequently and keeping up with the demands of our customers.

We’re announcing a $15M Series A funding and OpsLevel’s vision for accelerating software teams with developer portals.

Software developers have been putting badges on their repositories for a long time. Since they’re easily recognizable and have high information density, badges make it simple for developers to signal (or understand) things like code quality, test status and coverage, version, framework, or adherence to various standards.

With services, proper reliability is critical to success. But many don’t fully understand what reliability entails. In this post, we’ll set you up for success with an essential guide to understanding and improving service reliability.

Microservices will change. This is inevitable. But how do you manage that change to ensure your consumers don’t feel unnecessary disruption? Alternatively, what best practices can you follow to make migrations easy?

All over the globe, teams are scrambling right now to triage the impact of the recently announced Log4j vulnerability on their services and applications. Rather than reinvent the wheel, here’s a snippet from an informative Cloudflare blog post that puts CVE-2021-44228 in context:

Applications, products, and systems have become more and more complex. Microservices, dependencies, and external services provide greater functionality and improved reliability.

A security vulnerability was published on December 12th, 2021 by the NIST for Log4J version 2.14.1 or earlier, dubbed CVE-2021-4422. OpsLevel does not use Java in its technology stack and is not affected by this security advisory.