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.

Improving your microservice security isn’t like improving the security of a monolith application. Microservices provide lots of flexibility for application developers.

Snyk is rapidly becoming the de facto standard for businesses that want to build security into their continuous software development processes. And with their developer-first tooling and best-in-class security intelligence, it’s no surprise.

Over the last decade, shrinking feedback loops have been a core part of building and delivering software. Across every phase of development and delivery, software engineering organizations are getting faster answers to questions like:

Over the last week, the team at OpsLevel completed its largest HackDay ever. OpsLevelers demoed 15 different projects, spanning everything from our infrastructure and CI/CD pipelines to our Applicant Tracking System and assets for acquiring and onboarding customers. Even our CEO carved out time to write some code–though he admitted his UI was lacking.

Engineering initiatives are a necessity when it comes to ensuring security, reliability, and keeping the lights on within an organization. These can include actions such as upgrading library versions, migrating everyone to a new metrics provider, or upgrading a framework.

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.

With our Git Repository integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Previously, we’ve shown you a Repo File Check, which can be used to verify that a given file exists in your repo, or verify that it contains some specific text.

After setting up a Git Repository Integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Along with the integration comes two new checks: the Repo File Check and the Repo Search Check.