Developer

At OpsLevel we believe Service Ownership is the future of DevOps. We believe this subtle, but important, shift can bring tons of benefits to engineering teams: autonomy, speed, resiliency, and accountability. We build new features in OpsLevel with these characteristics in mind; that’s why we’ve recently launched automatically personalized dashboards for all OpsLevel users.

How we started: thumbnails with smartcropper. In the very early days of OpsLevel, our marketing website was powered by WordPress. Even though our site then was small, WordPress was a pretty big moving part that required more maintenance than it was worth. We found ourselves spending time on upgrading both WordPress and its plugins, debugging when things broke, and managing performance. We also found that drafts were not a great workflow for previewing or staging changes as the live production site wouldn’t always look the same as a draft edit.

Kubernetes is great because of its almost limitless configurability. But this configurability makes it hard to ensure that best practices are followed consistently across your cluster.

You can use OpsLevel’s Git Integrations to run code-level checks against your services, to bring ownership to your repos, and more. While the best way of integrating your repositories with OpsLevel is importing everything, we realize however that some repositories are more important than others. (cough 6-month-old hackday project cough.) Oftentimes these repositories aren’t ready to be archived or deleted, but also don’t need the full OpsLevel experience. Wouldn’t it benice if they almost didn’t exist at all in OpsLevel?

Having strong ownership of your microservices and other running systems is an important pre-requisite to building a DevOps culture. But focusing solely on ownership of services running in production can leave some gaps. There’s a lot of code living outside of any service’s codebase: libraries, internal tools, templates, terraform code, and a lot more. All of these repositories need ownership too.

Over the last few months at OpsLevel, we’ve changed how we tell interview candidates we’re not moving forward. Instead of a templated response, we now provide specific and actionable feedback for each candidate about where they fell short in our interview process and how they can improve. The results have been spectacular.

Last summer, our team gathered in the woodland heart of Parry Sound, Ontario for the inaugural OpsLevel HackDay. For 24 hours, participants were given total creative freedom while being tasked with creating a demo-able, team-based project. Skills were sharpened, bonds were strengthened, and marshmallows were roasted - it was a blast.

Pranav Krishnan is a Computer Science student at the University of Waterloo. I first started working at OpsLevel in May 2019 and it was my first ever co-op experience. I was extremely nervous, with no clue what to expect. Fast forward almost a year later and I find myself struggling with the idea of leaving this company behind.

A microservice catalog is only as good as the data it contains. OpsLevel is making it easier than ever to keep your service list up-to-date with its new Service Suggestions feature. With Service Suggestions, we automatically discover new services when they get deployed and help you add them to OpsLevel. For services that are already in OpsLevel, we can also help you easily attach those deployment streams to the right service.