Backstage Prometheus Plugin

Visualize key metrics and alerts of your infrastructure.

Created by Roadie

Getting started is simple

Don't want to spend your time installing and upgrading Backstage plugins? Get managed Backstage from Roadie.

Installation steps

The Prometheus plugin is a frontend plugin. You will need to install it, configure it and add it to an appropriate location on the entity page.

Install the Prometheus plugin into Backstage from the app folder of your repository.

cd packages/app
yarn add @roadiehq/backstage-plugin-prometheus

Setup a new proxy endpoint for the Prometheus API. Prometheus is unsecured by default but if you are running it behind a reverse proxy or other authentication mechanism, this proxy configuration can be used to define authentication method to use.

# app-config.yaml
    # url to the api and path of your hosted prometheus instance
    target: http://localhost:9090/api/v1/

(Optional) Additionally you can set up a different proxy path to be used by defining prometheus.proxyPath configuration

# Defaults to /prometheus/api/ and can be omitted if proxy is configured for that url
  proxyPath: /prometheus/api

The Backstage Prometheus plugin both entity content component and widget components.

Content Page Setup

// packages/app/src/components/catalog/EntityPage.tsx
import {
} from '@roadiehq/backstage-plugin-prometheus';
const serviceEntityPage = (
    <EntityLayout.Route path="/prometheus" title="Prometheus">
      <EntityPrometheusContent />

Widgets Setup

// packages/app/src/components/catalog/EntityPage.tsx
import {
} from '@roadiehq/backstage-plugin-prometheus';
const overviewContent = (
  <Grid container spacing={3}>
    <Grid item md={8}>
      <EntityPrometheusAlertCard />
    <Grid item md={6}>
      <EntityPrometheusGraphCard />

Add the EntityPagerDutyCard component to one or more entity page components depending on where you want the PagerDuty UI to appear. For example, display the PagerDuty UI on the existing Overview tab which is rendered for all types of entities.

// packages/app/src/components/catalog/EntityPage.tsx
const overviewContent = (
  <Grid container spacing={3} alignItems="stretch">
      <EntitySwitch.Case if={isPagerDutyAvailable}>
        <Grid item md={6}>
          <EntityPagerDutyCard />

Found a mistake? Update these instructions.

How it looks

Prometheus alerts and graphs rendered in Backstage.

Things to know


The Prometheus plugin is a frontend plugin that provides convenient access to frequently used Prometheus capabilities. Developers see pertinent information and actions for every entity that is connected to a Prometheus server.

The plugin provides an entity content page and two additional widgets:

  1. Alert table widget
  2. Prometheus Graph widget
  • Graph widget has two versions, line graph and an area graph

Entity annotations

The plugin uses entity annotations to determine what data to display. There are two different annotations that can be used:

  1. Rule annotation to visualize Prometheus recording rules and queries
  2. Alert annotation to display Prometheus alerting rule in a table format.


The ‘rule’ annotation expects a comma separated list of queries or recording rules and grouping dimension tuples. Dimension is optional and can be omitted which leads to the first label found from the returned data set to be used as the key to group items with.

The annotation supports individual metrics, promQL queries or references to a name of a recording rule. For complex queries a recording rule is the preferred option, since annotation parsing prevents the usage of characters , and | in queries.

Example annotation: memUsage|component,node_memory_active_bytes|instance,sum by (instance) (node_cpu_seconds_total)

Produces the following graphs:

  1. memUsage|component (grouping by component, otherwise __name__ would be the first item on this saved rule. Showed here as an area graph) Area Graph widget

  2. node_memory_active_bytes|instance (grouping by instance, image shows extra data on hover over a line.) Line graph with hover

  3. sum by (instance) (node_cpu_seconds_total) (instance is the grouper label defined in the query —> it is returned on the result set as the first label name, and is therefore used to group data with.) Line Graph constructed by query


The ‘alert’ annotation expects a comma separated list of predefined alert names from the Prometheus server. These are iterated and displayed in a table, displaying state, value, labels, evaluation time and annotations. To display all alerts configured in Prometheus a magic annotation all can be used.

Example annotation: 'Excessive Memory Usage'

Produces the following table. Alert table

Custom Graphs and Tables

For more customisability the package exports both PrometheusGraph and PrometheusAlertStatus as individual components. It is possible to create more customized graphs and/or tables using these directly by dynamically constructing props that these component are expecting.

Type definition for PrometheusGraph props is:

   query: string;
   range ? : {
      hours? : number;
      minutes? : number;
   step ? : number;
   dimension ? : string;
   graphType ? : 'line' | 'area';

Type definition for `PrometheusAlertStatus’ props is:

  alerts: string[] | 'all';

Become a Backstage expert

To get the latest news, deep dives into Backstage features, and a roundup of recent open-source action, sign up for Roadie's Backstage Weekly. See recent editions.

We will never sell or share your email address.