Dashboards in Rely allow your engineering teams to create and consume views that best tell the story and have answers for the use cases they care about

Dashboards in Rely allow your engineering teams to create and consume views that best tell the story and have answers for the use cases they care about:

• Onboarding engineers is a pain with scattered information across 10s of tools. They now have a view of everything they need to know from day 1
• A service your team depends on is behaving weirdly? Find all its performance metrics and owner’s communication channels at a glance
• To give you maximum value, Dashboards come to Rely out-of-the-box for the most common use cases
• Do you have use cases specific to your particular needs? Dashboards are entirely customizable end-to-end

‍

These are a few examples of use case-driven Dashboards that you can freely adopt and edit to make them best fit your business and needs.

Service Homepage

‍

As your teams last over time, they tend to both grow and renew themselves. 

The two or three developers present at the initiation of a project are no longer part of this same team after a year or two. 

The team now has 10 people in it and the onboarding experience for the number 4 and 5 is vastly different from number 10’s. So far tribal knowledge has been the norm to teach each new member about the scope of the team.

• What services are under its purview?
• For each service, where to find the most relevant resources like documentation or runbooks?
• Which Observability tools are used? Where are the links to the most relevant dashboards in these tools?
• How to find the running versions of this service in each environment?

‍

And these are just a few of the many many questions that new members ask about.

‍

And the same issue applies to external teams:

• Who owns this service that we need to shut down quickly for Resource maintenance?
• How to reach out to them?
• What’s the procedure to safely shut it down and restart it?

‍

To answer these questions and more, the Homepage is a reliable place to centralize the most important information about your entities in Rely.

‍

Performance Check-Up

Your teams know how to check the performance of their own applications and services. They just know that the APM telemetry is in New Relic, the Logs are in Datadog, and the metrics are in a Prometheus cluster. And for each of these tools, they know which dashboard to consult in specific situations.

‍

Experience shows however this tribal knowledge faces strong limitations when it comes to onboarding new engineers or making your key performance indicators available to other teams (who own for instance downstream Services). For these new members and external teams, it often boils down to chasing owners through channels and sifting through static (and often outdated) documentation.

‍

Centralizing not only key performance indicators but also direct links to the relevant dashboards enables all stakeholders—whether they're seasoned or new, and regardless of being internal or external—to establish robust, unified principles. 

• Standardization: the indicators are uniform and teams are expected to report indicators that allow comparison and analysis of trends.
• Quick access: the performance metrics are always found in the same view, readily available only a click away from the Homepage.

‍

With performance-dedicated dashboards, your teams can ship with confidence and transparency. They will have at-a-glance answers to typical questions like:

• What are the effects of the latest deployment?
• Does the service meet its SLO requirements?
• Are the error rate and latency kept in check with usage growth?

‍

The Observability view is an essential part of your developers’ workflow, both within and outside of their teams.

Deployment Analysis

As true followers of “you build it you won it”, engineering teams tend to put together their CI pipelines (and often their CD pipelines too) to best fit their workflows. With those in hand, they aim to ship fast and often.

‍

So tracking the latest changes in your applications can become once more a feat of tribal knowledge: staying up to date with the deployment process of each team. 

‍

With the Deployment View all stakeholders (Engineering Managers, dependent teams, new members, etc.) can get instant access to key information about the current deployment. 

‍

They can then answer questions like:

• What’s the latest image deployed in Production?
• Did it introduce any new code vulnerabilities?
• What were the results of the gating tests?
• How often does this service get deployed? How successful on average?
• What’s the deployment history for this service? (coming soon with the Pipeline widget!)

‍

These are examples of views engineering teams can benefit from out of the box or fully take over and customize to their own needs.

‍

Want to dive deeper into Dashboards in Rely?

• Experience them hands-on in our demo
• Reach out to our experts to explore how they can help your own use cases: link
• Keep reading to learn how to get started 👇

‍