Getting started with Perses — O11y Guide Part 6

A person using a laptop with graphs on it to analyze data for the Chronosphere.
ACF Image Blog

Learn about the origins of Perses, an open source standard for o11y dashboards and visualization, and how to install it on your systems.

Eric Schabell
Eric D. Schabell | Director of Technical Marketing and Evangelism | Chronosphere

Eric is Chronosphere’s Director of Technical Marketing and Evangelism. He’s renowned in the development community as a speaker, lecturer, author and baseball expert. His current role allows him to help the world understand the challenges they are facing with cloud native observability. He brings a unique perspective to the stage with a professional life dedicated to sharing his deep expertise of open source technologies, organizations, and is a CNCF Ambassador.


In this sixth installment of the series covering my journey into the world of cloud native observability, I’m going to start diving into an open source project called Perses. If you missed any of the previous articles, head on back to the introduction for a quick update.

After laying out the groundwork for this series in the initial article, I spent some time in the second article sharing who the observability players are. I also discussed the teams that these players are on in this world of cloud native o11y. For the third article I looked at the ongoing discussion around monitoring pillars versus phases. In the fourth article I talked about keeping your options open with open source standards. My last installment, the fifth article in this series, I talked about bringing monolithic applications into the cloud native o11y world.

Being a developer from my early days in IT, it’s been very interesting to explore the complexities of cloud native o11y. Monitoring applications goes way beyond just writing and deploying code, especially in the cloud native world. But one thing remains the same: Maintaining your organization’s architecture always requires both a vigilant outlook and an understanding of available open standards.

In this sixth article, I’m going to provide you with an introduction to an up and coming open source metrics dashboard project I’m getting involved in. Not only the introduction to the project, but I’m going to get you started hands-on with a workshop I’m developing to get started with dashboards and visualization.

This article is my start at getting practical hands-on experience in the cloud native o11y world. I’ve chosen to start with the rather new, up and coming open source project Perses. Not only am I exploring this project, but as I learn I am sharing this knowledge in a free online workshop that you can follow as it’s developed.

Now let’s explore the origins of this new project.

The origins of Perses

Perses is the first project under the CoreDash community umbrella which is part of the Linux Foundation. It’s a centralized effort to define a standard for visualization and dashboards. Perses is licensed under the Apache License 2.0, which is a big difference from the recent changes to what used to be the default dashboard project before they opted to change to Affero General Public License (AGPL) v3. This change means users the apply any modification have to share them back into the project, a bit more restrictive than most users want.

Its main goal is becoming an exploration into finding an open source standard for visualization and dashboards for metrics monitoring. Its first code commit was made on January 26, 2021, and since then has been quite active. There are clear project goals:

  • Become an open standard dashboard visualization tool.
  • Provide embeddable charts and dashboards in any user interface.
  • Target Kubernetes (k8s) native mode.
  • Provide complete static validation for continuous integration/continuous delivery (CI/CD) pipelines.
  • Architecture supporting future plugins.

Time will tell if these goals can be met, but you can check out a more in-depth introduction in this free online workshop lab 1.

Installing Perses

There are two options to install Perses on your local machine. One, you can build the source code project and run it from there, but there are a few software dependencies that you must meet first to do that. Second, if the bar is too high to build the project from its source, you can install and run Perses from a container image.

I’ve put together a simple supporting project you can use called the Perses Easy Install project. This project contains a simple installation script that allows you to either a container install using Podman, or to build the project from its source code. Both methods include sanity checks for the dependencies on your machine before allowing you to install the project.

Install in a Podman container

This is an installation using the provided Perses container image. You will run this container on a virtual machine provided by Podman.

Prerequisites: Podman 4.x+ with your Podman machine started.

  1. Download and unzip this demo
  2. Run ‘’ with the correct argument:
    • $ podman machine init
    • $ ./ podman
  3. The Perses container image is now running and pre-loaded with demo examples, connect in your browser:
    • https://localhost:8080

For an installation from source, the following process is needed.

Install on your local machine

This is an installation from the source code of the Perses project. You will test, build, and deploy the Perses server locally on your machine.

Prerequisites: Go version 1.18+, NodeJS version 16+, npm version 8+

  1. Download and unzip this demo
  2. Run ‘’ with the correct argument:
    • $ ./ source
  3. Perses is now running, connect to the Perses dashboards in your browser:
    • https://localhost:8080

For step-by-step instructions on how to install Perses using a container image or from the source code in the project itself, see this free online workshop lab 2.

Stay tuned for more insights into real practical experience as my cloud native o11y journey continues.

Check out the other articles in this series:
Part 7: Without observability, it’s just code
Part 5: Monoliths into the cloud native world
Part 4: Keeping your cloud native observability options open
Part 3: Cloud native observability needs phases
Part 2: Who are the cloud native observability players?
Part 1: Your first steps in cloud native observability

Share This:
Table Of Contents

Ready to see it in action?

Request a demo for an in depth walk through of the platform!