Personalized Ownership Dashboards in OpsLevel

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.

Ownership: front and center

One of our foundational capabilities is answering the question, who owns all these services?

Answering this broad question is invaluable to engineering leadership and also helpful in specific use cases. For example, a top-down view of your architecture is useful when tracking large scale migrations across your entire production infrastructure.

On a day-to-day basis though, most OpsLevel users are more narrowly focused. They want a clear picture of the services they own. They don’t want to search a catalog to find the things they care about. That’s where our new personalized dashboard comes in.

Personalized dashboard header in OpsLevel

As the screenshot above says, the dashboard summarizes everything a particular user owns within OpsLevel–services, repositories, and checks. Of course, ownership is based on team membership, so that’s also included on the dashboard. The new dashboard also serves as the home screen that users see each time they log into OpsLevel.

Less friction, more focus

Instead of being greeted by a long list of services and having to browse for the services their teams own, users can now access their unique view by default. This will save users time, but, more importantly, encourage them to review and evaluate ownership information on a more consistent basis–yielding a more accurate and more useful service catalog.

Personalized service ownership list in OpsLevel

Changing users’ standard entry point into OpsLevel may seem largely cosmetic, but we believe it will reduce friction in a variety of helpful ways, that add up to be very impactful:

  • Incident response: We expect the new dashboard to make it even simpler and faster for users to access information about their services (speed when it matters most).
  • Production readiness: We think the new dashboard will nudge engineers to examine the checks their services are failing, making accountability more natural and increasing the likelihood that they take proactive steps to up level their services!
  • Horizontal teams driving org-wide initiatives (e.g. a security team looking for vulnerabilities in open source libraries via Snyk): We believe checks should be front of mind, and evolve over time to meet an organization’s current context and objectives. Making it easier for check owners to access and review checks they’ve created ensures checks aren’t stale or outdated.

If you’d like to build a more autonomous and accountable engineering culture, learn more about OpsLevel, or see a personalized ownership dashboard in action, request your OpsLevel demo today.

Previous Post: Functional Teams Drive Service Ownership–Not HR Org Charts
Next Post: OpsLevel's Kubernetes Sync: Bootstrap and Enrich Your Service Catalog

Learn how to grow your microservice architecture without the chaos.

Not ready for a demo? Stay in the loop with our newsletter.