Visibility

A new blog series covering all the gritty details about how we dogfood OpsLevel on OpsLevel - #DogOps

For software developers working on complex distributed architectures, navigating boundaries is a recurring task. Depending on how narrowly their teams and services are scoped, much, or even most, of their work requires interacting with services they don’t own.

Lets review the ways you can ingest and manipulate data in OpsLevel. Whether you are new to OpsLevel, or a wily veteran, you’re certain to learn something along the way!

Many of us have tried setting goals in the past. Perhaps it was a required exercise for school or work, or we wanted to see if it could help us accomplish something. Results were mixed, and we often left goals unfinished.

Software engineering org charts have never been more complex. Gone are the days of large, stable teams that report to a single leader and work in highly structured ways on long-term projects.

Open source developer portal project Backstage hasn’t been on the scene for long. But in that time it has gained popularity quickly. The rate at which it’s added stars on GitHub is telling.

As a leader, onboarding with a new company is hard. The stakes are high–you and your new employer have invested a lot of time and energy into choosing each other–and the objective is complex–quickly go from an unknown outsider to a trusted leader. Oh, and make a positive impact on your team’s trajectory or output while you’re at it.

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.